[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev outofmem() allocating memory

From: Klaus Weide
Subject: Re: lynx-dev outofmem() allocating memory
Date: Wed, 7 Apr 1999 10:43:22 -0500 (CDT)

On Wed, 7 Apr 1999, Gisle Vanem wrote:

> Klaus Weide <address@hidden> said:
> >> This contradiction happens in libc's `fflush (stdout)'; it doesn't
> >> happen while in `fflush(stderr)' (because stdout is line-buffered).
> >
> > Except that *stderr isn't really the library-provided FILE you would
> > expect, if a Trace Log file is in use.  So you may have that problem
> > even for stderr.
> Really, I couldn't find that stderr is defined to something special,
> or that setvbuf() is used anywhere.

I was wrong about that, as far as the current code is concerned.  The
trace log code worked by assigning to *stderr in 2.7.?, but that has
been changed.

> >> BTW. YAMD (Yet Another Mallocing Debugger) is for djgpp and Linux.
> >>      It's available at <>
> > For the purposes of debugging lynx, how does it compare to lynx's
> > very own '--enable-find-leaks'?
> YAMD is more "low-level"; finds ptr-use after freeing, double-freeing,
> under or over-indexing dynamic data etc. I'm not sure 'find-leaks' can
> do that.

ptr-use no, double-freeing yes.  Not sure what is meant by {under,over}-

> The disadvantage is that it allocates a page (4kB) for every
> allocation! That's why I got outofmem() in the first place.

The advantage of lynx's builtin method is that it comes automatically
with lynx, and is easy to compile with (just one configure flag).
But no doubt more specialized libraries are more efficient.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]