Re: building and using dvdUNauthor

On Sat, 26 May 2012 07:28:43 -0500, Russell Urquhart wrote:

> Any GDB tips?

First of all, make sure everything is built with -g (include debugging
information).

Then, instead of running dvdunauthor directly, for example

    dvdunauthor foo

you do this instead (the “(gdb) ” is the default GDB prompt):

    gdb dvdunauthor
    (gdb) set args foo
    (gdb) run

Then, when it crashes and GDB redisplays its prompt:

    (gdb) bt

should give you a backtrace showing the source line where the crash
occurred, where that was called from etc.

Hopefully that should provide some clues as a start. Oh, and finally,

    (gdb) quit

to quit GDB. If the program being debugged is still running, you’ll get
asked if you really want to quit (and kill the debugged process); say
“y”.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Dvdauthor-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dvdauthor-users