This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: libSegFault and just in time debugging

Oops, hit send too soon...

Meant to say if you are automatically attaching to everything on the system, you have to be careful about auto-launched daemons, because they won't die all the way while waiting for the connection to the debugger, and that can cause them not to get restarted. Not a problem in general with released systems, where hopefully the daemons aren't crashing all that often. But with development systems it could cause a problem...


On Jun 29, 2007, at 1:12 PM, Jim Ingham wrote:

We did this with Mac OS X for a while (the way Mach Exceptions work it's a little easier to implement, you don't need a special library or anything like that). It's pretty neat. We were doing it automatically with all processes on the system, which is even handier, but you do have to be careful - if you are attaching with gdb rather than dumping core
On Jun 29, 2007, at 1:00 PM, Daniel Jacobowitz wrote:

On Fri, Jun 29, 2007 at 12:52:42PM -0700, Michael Snyder wrote:
Yes, apport is slick, but it relies on kernel mods.
This doesn't.  In fact, it isn't even peculiar to Linux, it would
work on any glibc system, and in principle even on systems
that don't use glibc.  Probably any unix, and even cygwin.

FYI, cygwin already does this, too; it can invoke dumper (to generate core
dumps) or GDB. I imagine you could invoke apport from a preloaded
library easily; after all, you can hook into it from Python exceptions.

Daniel Jacobowitz

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]