debuging woes

Charles Samuels charles at
Sat Jan 24 15:14:19 GMT 2004

Hash: SHA1

I'm not exactly sure what your problem is, but try running noatun with 
- --nofork when you debug.

Also, LD_BIND_NOW=1 in your environment will speed things up with gdb.

- -Charles

On Friday 23 January 2004 12:10 am, Darrell Esau wrote:
> Ok -- I'm working on a UI plugin for noatun (from kde 3.2beta)
> Everything was working great until some recent changes that I made to my
> plugin's user interface.  Now, when I load the plugin in noatun, it just
> dies silently (no core, no debuging information, nothing).
> I can put some printf statements in my plugin and I see them getting
> called up to a point (just before constructing an object).. then it all
> goes away.
> I've recompiled noatun with --enable-debug=full, but I still get nothing
> from noatun.  gdb tells me that there's no debugging information to be
> found.
> Checking kdebugdialog shows that area 0 has all debugging turned on (to
> stderr/stdout), and area 66666 has all debugging turned on (to
> stderr/stdout).
> Any suggestions on where to go from here?  I've fought with this for
> about 10 hours now trying to figure out where it's dieing.
> -d
> _______________________________________________
> kde-multimedia mailing list
> kde-multimedia at

- -- 
Charles Samuels <charles at>
Version: GnuPG v1.2.1 (GNU/Linux)


More information about the kde-multimedia mailing list