Index:
[thread]
[date]
[subject]
[author]
From: Christoph Egger <Christoph_Egger@t-online.de>
To : Jon M. Taylor <taylorj@gaia.ecs.csus.edu>
Date: Mon, 12 Jul 1999 22:45:52 +0200 (MEST)
Re: hacking methods to find out bugs
On Mon, 12 Jul 1999, Jon M. Taylor wrote:
> On Mon, 12 Jul 1999, Christoph Egger wrote:
>
> >
> > Hi all!
> >
> > I have tried to debug my lib with ddd again. Now I found some bugs, but
> > not all.
> >
> >
> > program exited with SIGSEGV at 0x400e807
> >
> >
> > How can I find out with this ddd error, what is buggy? I have no
> > experience about memory dumbing... Can anyone help me?
>
> What is usually do with a bugs like this is to fall back to using
> printf() (or the equivalent) to zero in on the line which is causing the
> segfault. Crude but often quite effective debugging technique. Once you
> have found the line which is causing the segfault, most of the time the
> problem will jump out at you.
Can you give an example?
Christoph Egger
E-Mail: Christoph_Egger@t-online.de
Index:
[thread]
[date]
[subject]
[author]