Hi all again, I have dug into the problem more deeply and found out that following environmental setting will help:
LD_PRELOAD=watchmalloc.so.1 MALLOC_DEBUG=WATCH,RW Thanks to that, the utility crashes exactly at the place the corruption takes place. The examination of the core in dbx told me that sprintf is actually a guilty one here. It allocates one byte more than the resulting string would need. I first though that using: LD_PRELOAD=libumem.so UMEM_OPTIONS=backend=mmap \ UMEM_DEBUG=default,firewall=1 will have the same effect as the previous env. settings, but this is not true. Regards Jan Jan Kopriva wrote: > Hi all, > > I have a strange problem. A utility I am using sometimes coredumps > SIGSEGV. If I use it with libumem preloaded it works perfectly. > Is there any debugging technique I can use in such cases? > > Thanks > > Jan > _______________________________________________ > mdb-discuss mailing list > mdb-discuss at opensolaris.org
