ubuntu-x-swat team mailing list archive
-
ubuntu-x-swat team
-
Mailing list archive
-
Message #96692
[Bug 666601] [NEW] Xorg does not dump core (via file nor Apport) on crash
Public bug reported:
I am attempting to report a segfault issue in xserver-xorg-core
2:1.9.0-0ubuntu7 in Maverick. However, I cannot get Xorg to dump a
usable core, whether into a file, or into Apport. I have done the
following:
1. Ensured that /etc/default/apport specifies a maxsize of 4GB
2. Added "ulimit -c unlimited" to /etc/init/gdm.conf (right before the
gdm-binary invocation)
3. Added NoTrapSignals option to xorg.conf
I've confirmed that #2 has taken effect by looking at
/proc/$xorg_pid/limits, and #3 does make Xorg's internal backtrace
handler disappear. But no core file appears in "/" (Xorg's cwd), or
crash report in /var/crash/ even with all these changes.
I'd also like to ask for some clarification as to whether the core-dump
ulimit applies only to core files, or if it also affects the core dumps
that get piped into Apport. Even when Apport is started at system boot
time, the core-dump ulimit is often set to zero, and that seems like it
might be a problem if you're hoping that Apport catches whatever goes
wrong.
** Affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
--
Xorg does not dump core (via file nor Apport) on crash
https://bugs.launchpad.net/bugs/666601
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
Follow ups
References