RE: [Dri-devel] Capturing debugging info without networking

2002-06-26 Thread Alexander Stohr

i would prefer this
  DRI_DEBUG_DIR=/var/tmp/dri_debug_`date +%Y-%m-%d-%T`
so that on sorted dir listings the most recent is
always on top since this date is encoded MSB first.
(textual month locales wont sort that good at all.)

another two things you might want to add:
  /sbin/lspci -vvv $DRI_DEBUG_DIR/lspci.txt
  /sbin/lsmod $DRI_DEBUG_DIR/lsmod.txt

do you expect this commands beeing executed as root
or as a user? you might want to add some suid root
detection or a su - query to the script lines.

hmm, is there a way to dectect what built in or 
external 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
 Subject: [Dri-devel] Capturing debugging info without networking
 
 
 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 to save info from the last crash. 
 Otherwise, just run it any old time to get a snapshot of log data.
 
 If there's interest, I'll put together a nice rc script that 
 should work
 on most distros for distribution with the testing binaries.  This is
 just a mock up (I haven't even run it - I hate dog food ;) of what
 should be a bit more complicated and grab a few more things, 
 but you get
 the idea.
 
 DRI_DEBUG_DIR=/var/tmp/dri_debug_`date +%d-%b-%Y-%T`
 mkdir $DRI_DEBUG_DIR
 cp /var/log/XFree86.0.log $DRI_DEBUG_DIR
 # this should work, but a grep might be better ...
 tail -5000 /var/log/messages $DRI_DEBUG_DIR/syslog.log
 cp /etc/X11/XF86Config* $DRI_DEBUG_DIR
 ls -l /usr/lib/libGL* $DRI_DEBUG_DIR/usr_GLFiles.txt
 ls -l /usr/X11R6/lib  $DRI_DEBUG_DIR/X11R6_libFiles.txt
 ldd /usr/X11R6/bin/glxgears $DRI_DEBUG_DIR/ldd_glxgears.txt
 
 # any other files ...
 
 tar -czf $DRI_DEBUG_DIR.tar.gz $DRI_DEBUG_DIR
 #rm -rf $DRI_DEBUG_DIR
 
 It might be nice to patch xinitrc to do this:
 glxinfo /var/tmp/glxinfo.txt
 every time so it can be bundled up, too.
 
 Then when people start having problems, the list can expect (somewhat)
 consistent reports.  Lemme know what you think.
 
 I take no responsibility for the meltdown of your system ;)
 -Al Tobey
 
 
 
 
 
 This email and any files transmitted with it are confidential
 and intended solely for the use of the individual or entity
 to whom they are addressed.  If you have received this 
 email in error please notify the Priority Health Information
 Services Department at (616) 942-0954.
 
 
 
 
 ---
 This sf.net email is sponsored by: Jabber Inc.
 Don't miss the IM event of the season | Special offer for 
 OSDN members! 
 JabConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn
 ___
 Dri-devel mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/dri-devel
 



---
This sf.net email is sponsored by: Jabber Inc.
Don't miss the IM event of the season | Special offer for OSDN members! 
JabberConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



RE: [Dri-devel] Capturing debugging info without networking

2002-06-26 Thread Sergey V. Udaltsov

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 | Special offer for OSDN members! 
JabberConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



RE: [Dri-devel] Capturing debugging info without networking

2002-06-26 Thread Alexander Stohr

some of the current desktop managers has those dial home 
feature with the fault handler built in. each crash could
get sent to the development team if the user likes it.

Maybe improved crash logging should get an integral feature 
of X11 on general platforms (of course embedded 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! 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 | Special offer for OSDN members! 
JabberConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel