On Oct 31, 2012, at 9:34 AM, Derek Atkins <de...@ihtfp.com> wrote: >> ----- Reply message ----- >> From: "Alex Aycinena" <alex.aycin...@gmail.com> >> Date: Wed, Oct 31, 2012 12:18 PM >> >> John, >> >> Just out of curiousity, do you know of any way to run the tests under >> gdb to step through them and see exactly where they fail? Since they >> are run from within make I've never been able to figure out how to do >> that. >> > > You need to modify the script to "exec gdb $program" .. >
No, don't do that. That's a real PITA, because the script gets rewritten every time you fix something. Do this instead: ../../../../libtool --mode=execute gdb test-backend-dbi You could save some thinking and typing by export LT=`pwd`/libtool from your top build directory and then you can do $LT --mode=execute gdb test-backend-dbi after cd-ing to the test directory. Regards, John Ralls _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
