Hi all
On 2006-04-12 15:05:38, [EMAIL PROTECTED] wrote:
> On Wed, 12 Apr 2006 08:13:47 +0200, ulisses said:
>
> > > : malloc(): Cannot allocate memory
> >
> > If we don't see the parameter of malloc I think we cannot help a lot.
> >
> > can you run the program with strace? that is, something like:
> >
> > strace -o myprogram.log ./myprogram
>
> Note that it would be the strange strace output indeed that captured the
> malloc, because strace catches system calls, and malloc() is a function call.
>
> You *might* catch a brk() or sbrk() system call, depending how your malloc()
> works. More likely, you'll be able to track down the failing malloc() by
> seeing
> what the last system call was, and from there figuring out where in the code
> it was.
>
I forgot it was a syscall, anyway it's possible to use ltrace wich catches
library calls too.
Ulisses
> Linking with a good debugging malloc that does extra sanity checking and
> tracing would probably be more productive. I can't recommend one in
> particular
> because I have no idea what system the original poster is on...
_______________________________________________
Flow-tools mailing list
[EMAIL PROTECTED]
http://mailman.splintered.net/mailman/listinfo/flow-tools
