* Curtis L. Olson -- Tuesday 04 June 2002 16:09: > If you send the debugt script to me, perhaps I can find a place in cvs > for it.
OK, I'll do so. But first I will beef it up, add some comments and security checks and all that. Basically if offers a few modes and sets up fgfs, valgrind and gdb for each: $ debug # runs "valgrind $fgfs" (interactive mode) $ debug -b # runs "valgrind $fgfs" (batch mode) $ debug -r # runs "$fgfs" $ debug -g # runs "gdb $fgfs" $ debug -c # runs "gdb $fgfs core" While options -r, -g, and -c don't look like a big gain, they guarantee that always the same binary is run and that you don't have to state the whole path every time. Additionally -g automatically starts gdb with the stated fgfs options, so you don't have to set them manually via gdb's 'set args ...'. Don't expect too much, though. It's just a simple bash script. :-) m. -- You don't seem to understand what being a maintainer means. It means saying no to crap. -- Linus TORVALDS _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
