Summary: | www-client/chromium is killed by pax | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | hardened |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | ht-wanted | ||
Package list: | Runtime testing required: | --- |
Description
Agostino Sarubbo
2013-08-28 14:22:53 UTC
It looks like Chromium crashed. You should probably use profile hardened/linux/amd64/no-multilib if you are using hardened kernel. (In reply to wbrana from comment #1) > You should probably use profile hardened/linux/amd64/no-multilib > if you are using hardened kernel. For which reason? You have probably non-hardened userspace with current profile which isn't compatible with hardened kernel. Conversion to full hardened userspace probably needs rebuild of most/all packages in correct order (1.gcc 2. glibc 3. others or something like that) after switching profile. More reliable way would be reinstall using hardened stage3. This crash can be also caused by some bug in Chromium or it was miscompiled because e.g. -march=atom -mtune=atom. (In reply to wbrana from comment #3) > You have probably non-hardened userspace with current profile which isn't > compatible with hardened kernel. From where this assumption is come from? Please also avoid to list the steps since I don't need them. You don't have hardened and pax_kernel in USE flags. Switching to hardened profile should add these flags automatically. (In reply to wbrana from comment #5) > You don't have hardened and pax_kernel in USE flags. Switching to hardened > profile should add these flags automatically. Grsecurity/pax is not designed to be used forced with the hardened toolchain. I don't need the hardened profile here nor the hardened IUSE. The pax_kernel IUSE in this case is not relevant. Agostino, it'd be great to obtain a stack trace from the browser if you can. Some helpful instructions can be found at https://code.google.com/p/chromium/wiki/LinuxDebugging It'd also be useful to know whether it's the main browser process, a renderer, or extension/app crashing. (In reply to Paweł Hajdan, Jr. from comment #7) > Agostino, it'd be great to obtain a stack trace from the browser if you can. > > Some helpful instructions can be found at > https://code.google.com/p/chromium/wiki/LinuxDebugging > > It'd also be useful to know whether it's the main browser process, a > renderer, or extension/app crashing. Pawel, this does not happens any time. I just found it im my log, so atm I just know that something go bad. (In reply to Agostino Sarubbo from comment #8) > Pawel, this does not happens any time. I just found it im my log, so atm I > just know that something go bad. I'll give it a little bit more time to see if anyone else can repro, but I'll eventually close the bug if there is no more precise info. (In reply to Paweł Hajdan, Jr. from comment #9) > I'll eventually close the bug if there is no more precise info. I gave what the log said, there are no more info about. (In reply to Agostino Sarubbo from comment #10) > (In reply to Paweł Hajdan, Jr. from comment #9) > > I'll eventually close the bug if there is no more precise info. > > I gave what the log said, there are no more info about. Thanks, closing. If this happens another time and you're able to capture something more, feel free to re-open. |