开发者

force coredump on glib free error

I get the following error when I run my program and it won't happen under gdb. How can I force glibc or ubuntu to dump core on abort? I tried "ulimit -c unlimited". But, this is not a seg fault and no luck. Also, I have too many memory errors in valgrind fixing all of them will take a lot of time.

Also, setting MALLOC_CHECK_ to 0 is not forcing program to exit. But, that's not a option for me.

* glibc detected ./main: free(): invalid next size (fast): 0x0000000000ae0560 **

Edit Anyway I found what is exactly causing this glibc corruption in valgrind. Just keeping i开发者_运维问答t open to see if it's possible.


From glibc documentation:

If MALLOC_CHECK_ is set to 0, any detected heap corruption is silently ignored; if set to 1, a diagnostic is printed on stderr; if set to 2, abort is called immediately.

Calling abort() usually produces a core dump (subject to ulimit -c setting).


Use Valgrind to diagnose and fix the problem. It will be quicker and straight to the point, since this indeed looks like a classic heap corruption.

There is likely a (Valgrind) package available for your distro, if you use a common one.

The only other method to create a core dump would be to attach GDB to the process before it happens. But that still doesn't get you closer to the solution of what causes the problem. Valgrind is the superior approach.

0

上一篇:

下一篇:

精彩评论

暂无评论...
验证码 换一张
取 消

最新问答

问答排行榜