[Pkg-chromium-maint] Chromium 14 backport "Aw, Snap!"

Fabien C. et1w9zppao6hlkl at jetable.org
Tue Oct 11 00:15:53 UTC 2011

> --renderer-cmd-prefix bypasses the sandbox

Damn it! I thought I had a workaround... The warning message telling
that the sandbox was disabled did not show up however.

> I followed the "connecting to a running renderer" process (and using
> --allow-sandbox-debugging), I've found that I can start debugging
> successfully. Yay :)

Hmmm, it seems to me that there is no "running renderer" to connect to,
simply because... it is crashed already. It is the very problem we
started this conversation for I think. :)

The problem is apparently coming from the chromium-sandbox (SUID binary)
which exits when launched.

$ gdb -p 15825
Attaching to process 15825
Reading symbols from /usr/lib/chromium/chromium...(no debugging symbols

(gdb) set follow-fork-mode child
(gdb) fg

// now you try to create a new tab: ctrl+T

[New process 15875]
[Thread debugging using libthread_db enabled]
process 15875 is executing new program: /usr/lib/chromium/chromium-sandbox
[Thread debugging using libthread_db enabled]

Program exited normally.
(gdb) quit

If I don't use the ----allow-sandbox-debugging, same scenario but I have
"Program exited with code 01" instead of "normally".

I tried to replace chromium-sandbox binary with the chromium 13's
version, but it doesn't work any better.

The chromium-sandbox code may need some investigation.


More information about the Pkg-chromium-maint mailing list