Re: malloc errors, HUGE stack

On Thu, Mar 18, 2004 at 04:52:09PM -0800, Norbert Kiesel wrote:
> Hi, I'm still hunting my "Could not allocate" bugs. I switched to Linux
> hoping they would go away, but they didn't. So no I put a sleep(60) into
> emalloc() afetr it prints this bug.   Please notice that this nessusd
> compiled with -O0 and statically linked against libnessus and libnasl.
> Version is 2.0.10a.
> 
>  First thing I noticed was that I have a HUGE stacktrace:
> Is this really intended?

Michel will know better, but I think that yes.

> Looking at the data in gdb, the len comes from the length parameter of
> "nasl_recv".  Is there any smart way to find out which nasl_recv of
> DDI_Directory_Scanner.nasl is processed at this stage?

Then the bug is probably in http_keepalive.inc, more specifically in
http_keepalive_send_recv(). However I don't see how the error can occur,
because there are size checks before the calls to recv().
Use display() to display the lengths :(
_______________________________________________
Nessus-devel mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus-devel