[MEncoder-users] MEncoder segfault

[Grozdan Nikolov]

>
> I'm not familiar with ddd.  In gdb, use the "bt" or "backtrace" command.
> I assume that ddd has a similar command.
>
> If the file that caused the segfault was compiled with -g, then the
> debugger should print out the source code filename and line number.  That
> makes finding the problem a *lot* easier.  Segfault is probably a bad
> pointer.
>
>
> (gdb) help stack
> Examining the stack.
> The stack is made up of stack frames.  Gdb assigns numbers to stack frames
> counting from zero for the innermost (currently executing) frame.
>
> At any time gdb identifies one frame as the "selected" frame.
> Variable lookups are done with respect to the selected frame.
> When the program being debugged stops, gdb selects the innermost frame.
> The commands below can be used to select other frames by number or address.
>

Sorry for the dumb question, but how do I run MEncoder under gdb? I've never 
done this here, I'm just a regular user, not a debugger.

Do I type on the command line: gdb bt /usr/local/bin/mencoder <parameters>
Can someone explain to me how to run MEncoder under gdb (the exact command 
line)?

Sorry for the dumb question