where are the chromium core dumps?

[Luigi Semenzato]

A browser crash on a test image built by myself does not yield any new
files in /home/chronos/user/crash or /var/spool/crash or
/var/log/chrome/Crash Reports, any idea why? The browser is NOT
oom-killed (the syslog would show that), and besides the problem
exists after a kill -SEGV.

[Mike Frysinger]

is the browser Chromium or Chrome ?  Chromium by default does not support crashes.

you can check by going to chrome://crashes

you should also consult /var/log/messages to see what crash-reporter thinks

-mike

[Luigi Semenzato]

Thanks.

On Tue, Jun 6, 2017 at 4:27 PM, Mike Frysinger <vap...@chromium.org> wrote:
> is the browser Chromium or Chrome ? Chromium by default does not support
> crashes.
>
> you can check by going to chrome://crashes

Yes it says "crash reporting is disabled". But crash reporting isn't
the same as core dumping no?

>
> you should also consult /var/log/messages to see what crash-reporter thinks
> -mike

Nothing there. Crash_sender runs every 2 hours, and says "exiting
early due to test image"

Also this site:

http://dev.chromium.org/chromium-os/how-tos-and-troubleshooting/debugging-tips

contains:

---------------
Enabling core dumps

Core dumps are disabled by default. To turn it on:

sudo touch /mnt/stateful_partition/etc/enable_chromium_coredumps
restart ui

Core files will be generated in the directory

/mnt/stateful_partition/encrypted/var/coredumps
or
/mnt/stateful_partition/var/coredumps
------------------

but that didn't help either.

I will try passing is_official_build=true to gn gen.

[Mike Frysinger]

On Tue, Jun 6, 2017 at 4:49 PM, Luigi Semenzato <seme...@chromium.org> wrote:
> On Tue, Jun 6, 2017 at 4:27 PM, Mike Frysinger <vap...@chromium.org> wrote:
> > is the browser Chromium or Chrome ? Chromium by default does not support
> > crashes.
> >
> > you can check by going to chrome://crashes
>
> Yes it says "crash reporting is disabled". But crash reporting isn't
> the same as core dumping no?

Chromium is responsible for creating its own crash reports and passing
them to the system crash reporter

i think you're conflating things though. nowhere are coredumps
fundamentally disabled. that's a feature of the kernel that we never
turn off.

after that you're talking about crash-reporter and how it handles
coredumps its been fed by the kernel and other processes. i don't
think we ever turn off the coredump->minidump process. there is a
knob that we turn on for dev/test images by default whereby we leave
the raw coredump alongside the minidumpified crash report.

after that, we get to what you seem to be asking about -- the browser
itself. Chromium takes care of processing its crashes and then
feeding them to the system crash-reporter. but if you build Chromium
(vs Chrome) by default, then the crash reporting logic is disabled.
sounds like that's what you did. enabling branding is probably the
easiest route.

the enable_chromium_coredumps knob is something the session manager
does. going by the code, that basically disables all the system crash
reporting logic in the system and tells the kernel to write its
coredumps to /var/coredumps/. whether that means even the Chromium
browser crashes are allowed to end up there i'm not sure ... i've
never needed to mess with that particular scenario.
-mike