Hey guys,
If its a memory problem often Electric Fence is useful in detecting the
error, it stops right on the line where you have the problem. Its a
static library so you'll have to compile it in to find the problem.
There are other utilities that will catch all sorts of problems that
will greatly alleviate your time spent in gdb or the necessity of
diagnostic printf() statements.
I can't remember the URL but you can find it with Google.
73s Jim Wantz WB0TFK
On Sun, 26 Aug
2001, Gregory Nowak wrote:
> Hi Chuck,
>
> Like you, I do that stuff too.
> However, I was hoping that gdb
> would make it easier, guess not (grin).
> Greg
>
>
> On Sun, Aug 26, 2001 at 07:54:17PM -0400, Charles Hallenbeck wrote:
> > Hi Greg -
> >
> > I will be interested to hear what some of the others have to say on this
> > one...
> >
> > What I do with my own programs is to try to narrow the problem down by
> > inserting very simple "marker" output statements at strategic points in
> > the source code, recompiling, and studying the new output. There is surely
> > a better way, but for me "setting traps" like that has worked. I would
> > hate to have to do that on a program with which I was not intimately
> > familiar though! Tough enough on my own monstrosities, let alone someone
> > else's.
> >
> > Chuck
> >
> >
> > Visit me at http://www.mhonline.net/~chuckh
> > The Moon is Waxing Gibbous (61% of Full)
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup at braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
