RFC: Automatic trouble reporting

Johan Walles walles at mailblocks.com
Wed Feb 2 01:51:32 CST 2005


Hadn't heard about catchsegv before, you learn something new every day 
:-).

Its output looks like a good start; it needs to be decorated with 
package names and versions though.  As long as I know that any time 
anything crashes on my system, somebody gets notified without me having 
to do anything, I'd be happy.

Also, it needs to be loaded through /etc/ld.so.preload, doing it from 
gnome-panel (don't know if this was just a typo) will still mostly 
catch GNOME stuff.  If X or sshd or something like that crashes, you 
need to be a bit more daring than that to catch it.

  Regards //Johan

-----Original Message-----
From: Mike Hearn <mike at navi.cx>
To: ubuntu-devel at lists.ubuntu.com
Sent: Sun, 30 Jan 2005 12:46:43 +0000
Subject: Re: RFC: Automatic trouble reporting

On Sun, 30 Jan 2005 01:45:43 -0800, Johan Walles wrote:
> As you say, bug-buddy covers only Gnome.  If anything non-Gnome 
crashes
> it won't help.  For example if the X server crashes, bug-buddy won't 
be
> of much help, but that's something you'd probably want to know about. 

> And if any non-supported Gnome software crashes, what happens with 
the
> bug report?

That's a completely solvable problem, which is somewhere near the bottom
of my perpetually changing to do list. Look at the catch-segv program 
that
ships with glibc: using an LD_PRELOAD library to replace the default 
fatal
signal handling is easy and relatively safe. It could be done by
gnome-panel and the current signal handling code in libgnome deprecated.

thanks -mike


--
ubuntu-devel mailing list
ubuntu-devel at lists.ubuntu.com
http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel


----------------------------------------------
Mailblocks - A Better Way to Do Email
http://about.mailblocks.com/info




More information about the ubuntu-devel mailing list