folks wont like it).
> -Original Message-
> From: Sergey V. Udaltsov [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, June 26, 2002 21:23
> To: Alexander Stohr
> Cc: Al Tobey; DRI
> Subject: RE: [Dri-devel] Capturing debugging info without networking
>
>
> Good boys
I'll first get a nice easy script working. If it proves a hit with
developers, I'll script out a gdb backtrace on the X server, just in
case it crashed. This might require a small X client that keeps trying
to update itself (say, every second), which triggers the backtrace when
it fails. Just a
Good boys! Can anyone invent the way to do the same thing with gdb? So
on X crash one could get backtrace without remote debugging...
Cheers,
Sergey
---
This sf.net email is sponsored by: Jabber Inc.
Don't miss the IM event of the season | S
l modules a specific linux kernel does provide?
why are you using ">>" for some of the redirections?
what about a final bz2 tarball creation?
> -Original Message-
> From: Al Tobey [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 25, 2002 23:39
> To: DRI
&
Here is a sort of simple shell script that I just thought of that might
make people's lives a little easier. Cut & paste this into a file
(maybe /usr/local/bin/dri_debug.sh) and then add this line to your
equivalent of /etc/rc.local:
/bin/sh /usr/local/bin/dri_debug.sh
to have it run at boot time
