GDB: debugging closed code

Question

I´m working with an application (closed sources, i don´t have the sources) that allows me to plug in my customizations developed in c (my own code, i have the sources) that are called by the main process via call backs, it like to have plugins.

When we try to debug the execution of this program, it fails trying to get the sources of the main program, as its closed source i don´t have it.

how can i debug this program? how can i configure gdb avoiding that it tries to retrieve the closed sources?

i´m working on hp-ux and i want to find memory leaks in my code.

Thank you very much!

Answer 1

When we try to debug the execution of this program, it fails trying to get the sources of the main program, as its closed source i don´t have it.

This is just a warning from GDB; one you can safely ignore.

how can i debug this program?

The usual way. Debugging will be harder because you can't see the main application sources, but (assuming you only care about debugging your own code) not too hard.

how can i configure gdb avoiding that it tries to retrieve the closed sources?

You can't, but it's not an error, and shouldn't prevent you from doing anything.