A few moons ago we have discussed on the dev list a tool for automatic
segfault detection (including multiple segfaults during 'make test') and
core backtrace generation. I'm quite frankly tired of explaining again
and again that we need a core file backtrace, how to get the core file
dumped
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
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
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
Date: Fri, 12 Apr 2002 00:24:11 +0800
To: [EMAIL PROTECTED]
From: Stas Bekman [EMAIL PROTECTED]
Subject: Challenging things to do: SIGSEGV catcher and backtrace extractor
Message-ID: [EMAIL PROTECTED]
A few moons ago we have discussed on the dev list a tool for automatic
segfault
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.
