Your message dated Sun, 22 Jul 2007 02:13:07 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#108451: X server should dump traceback on fatal signals
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: xserver-xfree86
Version: 4.0.3-4
Severity: wishlist
Fatal server error:
Caught signal 11. Server aborting
When reporting a problem related to a server crash, please send
the full server output, not just the last messages.
This can be found in the log file "/var/log/XFree86.0.log".
Please report problems to [EMAIL PROTECTED]
This after about five hours running the server. Which has been run without any
configuration changes for weeks. Needless to say, no relevant messages
immediately above in the log -- just the usual noise.
It would be useful in these cases to dump a full stack traceback to the log, so
the faulty function could be more easily located. Since X already does complex
things in the signal handler (it returns to text mode!), it shouldn't be too
hard (and no need for symbols, they can be gotten from the binary later).
-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux flower 2.4.7 #1 Sat Jul 21 20:57:24 BRT 2001 i686
Locale: LANG=en_US.ISO8859-1, LC_CTYPE=en_US.ISO8859-1
Versions of packages xserver-xfree86 depends on:
ii debconf 0.9.81 Debian configuration management sy
ii libc6 2.2.3-9 GNU C Library: Shared libraries an
ii xserver-common 4.0.3-4 files and utilities common to all
ii zlib1g 1:1.1.3-15 compression library - runtime
--- End Message ---
--- Begin Message ---
On Sun, Aug 12, 2001 at 00:08:41 -0300, Cesar Eduardo Barros wrote:
> It would be useful in these cases to dump a full stack traceback to
> the log, so the faulty function could be more easily located. Since X
> already does complex things in the signal handler (it returns to text
> mode!), it shouldn't be too hard (and no need for symbols, they can be
> gotten from the binary later).
>
As far as I can tell, that's what happens today (not sure since when,
but). I'm thus closing this bug.
Cheers,
Julien
--- End Message ---
