SMOP Debugging: Revision 2
Debugging a libtool package is not that straight forward because of the libtool scripts, which gdb doesn't like at all.
First thing, you need to get a debug-friendly compilation, to get that you need to do:
Then, to debug, let's say test/01_smop_lowlevel.t, you must:
This is needed because libtool puts the actual binaries in a .libs directory, and gdb is not happy debugging the script libtool places in the place of the executable.
If you want to run valgrind to check for memory leaks not reported by the SMOP_LOWLEVEL_MEM_TRACE, you can just
See also SMOP Hacking