On Wed, 2006-11-01 at 10:15 -0500, Andrew Conkling wrote: > I'm totally not giving up on debugging Banshee for all it's worth. > There are a few bugs I've found in Bugzilla that I can easily > reproduce that don't have BTs. Since I just installed debug packages > for most of my software, including Banshee, I'd like to get backtraces > for them. > > However, I can't seem to get Banshee to run within gdb. The > instructions (http://www.mono-project.com/Debugging), chock full of > useful things to do with gdb, don't indicate how to get started. > Here's what I've tried with the errors I get: > > $ (Trying 3 ways to Sunday, e.g. "gdb banshee") > (gdb) run > Starting program: > No executable file specified. > Use the "file" or "exec-file" command. > > $ gdb mono > (gdb) run /usr/lib/banshee/banshee.exe (snip) > > The first makes some sense; the second less so, but all in all, I'm > just not sure how to get it going. I think it has something to do with > all that the /usr/bin/banshee script sets up, but I don't know how to > do that in gdb, and running the shell script directly doesn't work. > > Any help would be great; let's target these bugs! > > Cheers, > Andrew http://banshee-project.org/Debugging has a bunch of tips for getting gdb to work nicely with banshee. Most of them are also at mono-project, but since the banshee instructions can be more specific, there's a better S/N ratio than in the instructions at mono-project.com -Mark Gordon
Attachment:
signature.asc
Description: This is a digitally signed message part