This bug was fixed in the package xorg-server - 2:1.5.99.3-0ubuntu3
---
xorg-server (2:1.5.99.3-0ubuntu3) jaunty; urgency=low
[Timo Aaltonen]
* debian/rules: Disable builtin fonts (LP: #308649)
[Bryce Harrington]
* 135_rethrow_signals.patch: Update for 1.6 and re-enable.
Previous patch was missing some important bits, causing it to FTBS.
Here's the more complete version. I also updated it to apply to 1.6
without any fuzzy matching.
** Attachment added: "135_rethrow_signals.patch"
http://launchpadlibrarian.net/20484488/135_rethrow_signals.patch
--
Xorg crash
Bryce and I finally tracked it down. This is the updated
135_rethrow_signals.patch.
** Changed in: xorg-server (Ubuntu)
Status: In Progress => Fix Committed
** Attachment added: "fixed patch"
http://launchpadlibrarian.net/20358645/135_rethrow_signals.patch
--
Xorg crashes do not work
Hmm, you know in thinking about it more, I bet I had this set on the
system I had done the initial development on:
Section "ServerFlags"
Option "NoTrapSignals" "true"
EndSection
(Our backtracing docs suggest having this on for debugging purposes -
https://wiki.ubuntu.com/X/Backtracing)
H
What's weird is that this *was* working a little while ago. See bug
274693 for example. 284470 is a fresh one from yesterday with fairly
up-to-date intrepid. I'd expect it to either work, or not work, but it
appears to be working *sometimes*.
Also, when I was testing the most recent version of
Thanks for the additional analysis Martin, glad it wasn't just a trivial
oversight on my part!
I spoke with Colin about this. I will keep working on this with a focus
to get it in early in jaunty. Since apport is used more during the
development period than after release, this probably makes the
Hm, I changed the raise(signo) to kill(getpid(), signo). The strace
duefully now has kill() instead of tgkill(), but it doesn't help. It
just doesn't coredump. When X exits,it doesn't even show "+++ killed by
SIGSEGV".
--
Xorg crashes do not work with apport
https://bugs.launchpad.net/bugs/226668
I built an X server with this patch and tested it. However, apport does
not seem to be called at all. The X.org log says "re-raising 11", and in
strace I see:
7363 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
7363 rt_sigaction(SIGSEGV, {SIG_IGN}, {0x80b4ce0, [SEGV], SA_RESTART}, 8) = 0
[...]
736
X server has it's own signal handler which is what catches failures and
prints the backtrace in the log. The signal handler doesn't re-raise
the signals it handles, and instead simply abort()'s.
** Attachment added: "reraise_signals_5.patch"
http://launchpadlibrarian.net/18600200/reraise_sign
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => In Progress
--
Xorg crashes do not work with apport
https://bugs.launchpad.net/bugs/226668
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
** Changed in: xorg-server (Ubuntu)
Importance: Undecided => Wishlist
Assignee: (unassigned) => Bryce Harrington (bryceharrington)
Status: New => Confirmed
--
Xorg crashes do not work with apport
https://bugs.launchpad.net/bugs/226668
You received this bug notification because you
** Attachment added: "lshw-output.txt"
http://launchpadlibrarian.net/14207560/lshw-output.txt
--
Xorg crashes do not work with apport
https://bugs.launchpad.net/bugs/226668
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
12 matches
Mail list logo
