On Thu, Oct 16, 2003 at 10:17:45PM +0400, Nikita V. Youshchenko wrote:
> You misunderstood me.

Sorry about that.

> I know about this package.
> But I would like to know what will be next after 45 megabyte download (a 
> large one for me).
> I can't just run it under gdb on non-networked workstation - I will get a 
> system hang on the crash event.
> The question was - how to get a crashed server's core? Perefably without 
> human interaction - the machine in question is located at user's home, I 
> can't sit for hours there waiting for a crash ...
> 
> If there is documentation in xserver-xfree86-dbg, just tell me about it, 
> and I will proceed and download it.

Okay, here's what I suggest:

1) Ensure the user is not using a display manager (xdm, gdm, wdm, kdm).
   Have them use startx instead.
2) Install xserver-xfree86-dbg and make it the default X server (there
   is a debconf question about this).
3) Check the target of the /etc/X11/X symlink and make sure it points to
   /usr/bin/X11/XFree86-debug.
4) Make sure the X user's core dump size is unlimited.  "ulimit -c
   unlimited" should do the trick.  Ensure this is done *before* using
   startx to start the X server.
5) Edit /etc/X11/XF86Config-4 and add the following section:

   Section "ServerFlags"
     Option "NoTrapSignals"
   EndSection

   (If a "ServerFlags" section already exists, just add the Option line
   to it.)  Ensure this is done *before* using startx to start the X
   server.
6) Wait for the X server to crash.
7) The machine will likely be locked or unresponsive, since when
   NoTrapSignals is set, the X server will not be able to reset the
   video card and switch back to a console VT, and won't be around
   anymore to listen for CTRL-ALT-F1, for example.  The computer may
   have to be hard-rebooted or power-cycled.
8) When you are back to a shell prompt, a file called "core" should be
   in the directory from which the "startx" command was run.
9) Become root and "apt-get install gdb" if it's not already installed.
10) Run the command "gdb $(which XFree86-debug) core".
11) At the gdb prompt, run the command "bt full".
12) File a bug report with the Debian BTS.  I suggest using the
    "reportbug" command.  Don't forget to include the output of "bt
    full".

Please let me know if you have any questions about the above procedure.

-- 
G. Branden Robinson                |    It may be difficult to to determine
Debian GNU/Linux                   |    where religious beliefs end and
[EMAIL PROTECTED]                 |    mental illness begins.
http://people.debian.org/~branden/ |    -- Elaine Cassel

Attachment: signature.asc
Description: Digital signature

Reply via email to