Unexpected core by signal 11 (heap corruption)

[Dennis Handly]

Were you able to use gdb's heap checking options to track down the heap corruption?

Otherwise I would need access to the WHOLE application and the corefile.

[Alex Pronichev]

My application is very big.
Core file size is above 100Mb
Application has many modules and libraries, and has a connection with delivery system.
I can't do access for you to our test server.
What kind of information do you need?

[Dennis Handly]

>My application is very big.
Core file size is above 100Mb
Application has many modules and libraries, and has a connection with delivery system.
I can't do access for you to our test server.
What kind of information do you need?

I would need access to everything in order to see why the heap is corrupted. In the worst case I would have to run it with watch points to see what corrupts it.

But you have never said if you were able to use gdb's heap checking options?

[Dennis Handly]

Did you ever solve this?

>I also use GDB with keys: set heap-check bounds on
but this haven't any result

The syntax may have caused this to not work. You need to do:
(gdb) set heap-check on bounds on