> > Hi,
> > I have difficulties with a Termination on signal 11 error .
> > Someone told me that this points to a misuse of memory
> Yes. Signal 11 is SIGSEGV => Segmentation Fault. It indicates you've
> accessed memory you don't own.
> > and indeed as tried to avoid the signal with
> > signal(11,SIG_IGN)
> That merely masks the bug you have, and doesn't help fix it at all.
> Don't do this.
Actually, do it if you want...it'll have no effect. You
can't ignore a SIGSEGV.
> > i got a segmentation fault .
> > Is there a way to use a signalhandler to get more
> > information about the place where the misuse of memory
> > occoured ?
Well, there is, but it's probably not what you want. Unless
you know _exactly_ what you're doing, you can't reasonably
recover from it anyway.
> Run your program under a de*. When the signal hits, you'll drop
> back into the de*, and can then examine what was happening at the
Further hint: if you discover that your SIGSEGV has occurred
in a malloc() or free(), for example, you've most likely
overrun a buffer somewhere (munging the allocator's internal
state or the meta-data attached to an allocated object)
_before_ the SIGSEGV actually occurs.
Artie Gold, Austin, TX (finger the cs.utexas.edu account
for more info)
Verbing weirds language.