2 Sep
2010
2 Sep
'10
4:30 p.m.
On Fri, 2010-08-20 at 15:26 -0500, Martin Holste wrote:
Glad to hear it's mostly working. In a pinch, you can always run the program under gdb (remember to use "set args" on any params after the program name) and then use "bt" to get a somewhat helpful backtrace. It usually is enough to nail down the general area of code that is having an issue. So if your command normally looks like this: "bin/pdbtool test -p var/patterndb.xml" you would run "gdb bin/pdbtool" then "set args test -p var/patterndb.xml" inside gdb and finally "bt" (or whatever) when it segfaults.
you can always use gdb --args pdbtool test -p var/patterndb.xml this is the same as using an explicit set args command. -- Bazsi