Re: Challenging things to do: SIGSEGV catcher and backtrace extractor

2002-04-11 Thread Doug MacEachern
On Fri, 12 Apr 2002, Stas Bekman wrote: If you read the rest of the post I mention it (without telling the name :). The problem with this module is that it's useful only after you have the core file. which is not good, because (as I've already explained): it's important to mention

Re: Challenging things to do: SIGSEGV catcher and backtrace extractor

2002-04-11 Thread Stas Bekman
Doug MacEachern wrote: On Fri, 12 Apr 2002, Stas Bekman wrote: If you read the rest of the post I mention it (without telling the name :). The problem with this module is that it's useful only after you have the core file. which is not good, because (as I've already explained): it's

Re: Challenging things to do: SIGSEGV catcher and backtrace extractor

2002-04-11 Thread Doug MacEachern
On Fri, 12 Apr 2002, Stas Bekman wrote: You can get a backtrace if you run the process under debugger without dumping a core file. No special setup required. I was thinking to attach the debugger on SIGSEGV event. Is it too late? I see certain gnome apps failing and they ask you if you

Re: Challenging things to do: SIGSEGV catcher and backtrace extractor

2002-04-11 Thread Daniel Jacobowitz
On Fri, Apr 12, 2002 at 02:09:44AM +0800, Stas Bekman wrote: Doug MacEachern wrote: On Fri, 12 Apr 2002, Stas Bekman wrote: If you read the rest of the post I mention it (without telling the name :). The problem with this module is that it's useful only after you have the core file.