gnupic: I'm crashing the GUI in gpsim 0.20.X. Any ideas?
Subject:
Re: I'm crashing the GUI in gpsim 0.20.X. Any ideas?
From:
"Philip Restuccia" ####@####.####
Date:
4 Oct 2001 12:07:53 -0000
Message-Id: <3BBC5091.D8479B32@nortelnetworks.com>
Scott Dattalo wrote:
>
> On Wed, 3 Oct 2001, Byron A Jeff wrote:
>
> > However I've run into a problem. I'm using gpsim for testing. It had been
> > working just fine with the GUI until I added/moved quite a bit of code.
> > All of a sudden it starts segfaulting upon startup. Upon debugging I
> > discovered that it was failing on a malloc deep in the C library.
> >
> > But it's flaky. It works fine a time or two then a string of segfaults.
> >
> > Any clues where I should start looking?
>
> Try running gpsim under gdb. When it crashes, dump the stack trace
> (backtrace). This will at least pin point where the malloc is failing.
> You can send me the trace to.
A word of warning, based on years of experience (sigh ...) with this type
of problem. A segfault in a malloc is often due to a corrupted heap. The
corruption is, unfortunately, often CAUSED by code that was executed possibly
LONG before the malloc that DETECTED the corruption by segfaulting :-)
Years ago, these types of problems were EXTREMELY tedious to find; often
the only way was through the use of printf statements carefully sprinkled
around your code, sloooooooowly closing in on the actual code that was causing
the heap corruption.
Nowadays, of course, the's Purify :-)
Philip
--
Philip Restuccia
Senior Principal Software Engineer
Nortel Networks
####@####.####
