From: Christoph Egger <Christoph_Egger@t-online.de>
  To  : Ville Hallik <Ville.Hallik@mail.ee>
  Date: Wed, 14 Jul 1999 09:08:18 +0200 (MEST)

Re: hacking methods to find out bugs

On Wed, 14 Jul 1999, Ville Hallik wrote:

> On Tue, 13 Jul 1999, Christoph Egger wrote:
> 
> > On Tue, 13 Jul 1999, Ville Hallik wrote:
> > > 
> > > But You can raise SIGSEGV again after cleanup and voila: coredump is here.
> > > This works at least for the following simple program under glibc2.1
> > > (core shows exactly the right crashpoint: *p = 'a'; ):
> 
> [code example removed]
> 
> > Can you give an more common example that works under glibc2.0 too?
> 
> Same example works perfectly under RedHat-5.2 (glibc2.0 based system).

I have a SUSE 6.0 based system with kernel 2.2.10
SUSE 6.0 is based on glibc2.0. And I don't get a core dump, only when I
run it with gdb...

> Unfortunately, coredump is not very helpful under libc5 based system I
> have access to, but running under debugger still shows the exact location
> of the crash. But this may be gdb's problem.
> 

ok - I see I don't learn out... :)

Christoph Egger
E-Mail: Christoph_Egger@t-online.de