Re: [Sheflug] Segfaults & ld.so wierditude

[Alastair Donlon <nospam [at] netsoc.ucd.ie>]

On Tue, May 02, 2000 at 11:38:46AM +0100, Bob Ham wrote:
> On Fri, 28 Apr 2000, Stephen J. Turnbull wrote:
> 
> > >>>>> "Bob" == Bob Ham <u9rah [at] dcs.shef.ac.uk> writes:
> > 
> >     Bob> Anyway, that problem solved, and another one reared it ugly
> >     Bob> head again.  It's a different program, but the code is part
> >     Bob> of the same project.  The problem is in malloc().
> > 
> > Sounds to me like you've got a bogus pointer somewhere that's
> > overwriting malloc's private data.
> 
> It's that malloc() itself segfaults, as in in the backtrace I get
> strdup(), malloc(), malloc() right at the top.
> 

Segfaults during malloc() usually point (ha, what a pun) to a double
free() somewhere in the code. Free'ing the same pointer twice does
BadThings(tm) to mallocs internals.

A.D.

---------------------------------------------------------------------
Sheffield Linux User's Group - http://www.sheflug.co.uk
To unsubscribe from this list send mail to
- <sheflug-request [at] vuw.ac.nz> - with the word 
 "unsubscribe" in the body of the message. 

  GNU the choice of a complete generation.