[TH - 64] Chromium chromoli po upgrade

[Elan Ruusamäe]

On 12.02.2013 12:23, Elan Ruusamäe wrote:
> as much i understood reading the bugreport then "segfault at NUMBER", 
> means syscall NUMBER in HEX, the reports you referred had 0x19, but 
> our (yours and mine) are 0x122 hex (290 dec) which is different syscall:
>
> Feb 11 19:38:59 blodnatt kernel: : [  375.154516] 
> chromium-browse[3544]: segfault at 122 ip 00007f3f9c5ea353 sp 
> 00007f3f865e5330 error 6 in chromium-browser[7f3f9b794000+3e95000]
> Feb 11 19:39:00 blodnatt kernel: : [  375.292081] 
> chromium-browse[3551]: segfault at 122 ip 00007f3f9c5ea353 sp 
> 00007f3f865e5330 error 6 in chromium-browser[7f3f9b794000+3e95000]
> Feb 11 19:39:00 blodnatt kernel: : [  375.857206] 
> chromium-browse[3563]: segfault at 122 ip 00007f3f9c5ea353 sp 
> 00007f3f865e5330 error 6 in chromium-browser[7f3f9b794000+3e95000]

> ...
> Feb 11 19:40:31 blodnatt kernel: : [  466.530506] 
> chromium-browse[4978]: segfault at 122 ip 00007fc083ddb353 sp 
> 00007fc06ddd6330 error 6 in chromium-browser[7fc082f85000+3e95000]
>
>
> $ grep  -r  __NR_.*290 /usr/include/asm
> /usr/include/asm/unistd_32.h:#define __NR_ioprio_get 290
> /usr/include/asm/unistd_64.h:#define __NR_eventfd2 290
> /usr/include/asm/unistd_x32.h:#define __NR_eventfd2 (__X32_SYSCALL_BIT 
> + 290)

found only 1 bug matching same segfault at pattern:
https://code.google.com/p/chromium/issues/detail?id=169421



-- 
glen