Libc6 malloc bites?

Tomasz Ciolek tmc at
Sat Sep 1 12:25:19 EST 2001

 Perl has its own malloc. Is it possible someone complied the package using perlmalloc and not the Linux malloc?

 I'm not having any problems with perl proggs (wunning current woody)


On Sat, Sep 01, 2001 at 11:07:52AM +1000, Tim Potter wrote:
> jeremy at writes:
> > >> Am I correct in thinking that this is malloc from libc causing the
> > >> trouble?  Is there a chance that going forwards or backwards a
> > >> version will help?
> > > 
> > > It could equally be a problem with the Perl you are running.  If
> > > malloc is passed a bad pointer, there is little it can do to avoid
> > > eating out its own entrails and dumping core.
> > 
> > OK, cool.  Can you tell me how I could check to see if malloc is being
> > passed a bad pointer?
> > 
> > I don't really mind what I file a bug report against, just that the
> > problem gets duly noted.
> If you can boil the problem down to a small reproducible test
> case you can probably post it to comp.lang.perl.something and
> someone will probably notice it.  Or failing that some perl
> devel list will do.
> A few years ago I thought up a really hairy regular expression
> that crashed perl, posted it to clpm and it was fixed in a couple
> of hours!
> Tim.

Tomasz M. Ciolek	*
			* 	Everything falls under the law of change;	
<tmc at>	*	  Like a dream, a phantom, a bubble, a shadow,
<tmc at>	*	  like dew of flash of lightning.
			*	  You should contemplate like this. 
GPG Key ID: 0x7A18E49D	*	Available on

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
Url :

More information about the linux mailing list