On 11.03.10 16:03, Pierre-Olivier Gaillard wrote:
Hi all,
I have a program that crashes. From the stack I suspect it's trying to read
free memory, probably because it's trying to clean some structures twice.
Unfortunately I can't run the program under Purify as it's a 32 bit program
and the purify runs out of 4GB. So I tried libumem as I think it should be
able to find the error but libumem is running out of memory too.
I am now trying to reduce the logging some more in the hope that the
program will run:
LD_PRELOAD="libumem.so.1"
UMEM_LOGGING='transaction'
UMEM_DEBUG='audit,guards,verbose'
My other idea is to try to emulate the feature I want from these tools with
dtrace and a huge log file:
- trace all malloc and free, including stack, address and size
I'd add a trace that is triggered when the program dumps core (elfcore, eg,
IIRC) and print ustack() here.
- wait for the crash
can you examine the core dump?
Michael
--
Michael Schuster http://blogs.sun.com/recursion
Recursion, n.: see 'Recursion'
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
