| Summary: | amarokapp does not produce debug information | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Nick Hawes <n.a.hawes> |
| Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Nick Hawes
2005-05-26 10:13:36 UTC
In case it's relevant: I'm using gstreamer engine + alsa sink. Sorry, this doesn't belong in a bug report. Anyway, please paste your whole ./configure line. And state what you actually built (our original source tarball?) Configure line: ./configure --enable-debug=full --prefix=`kde-config --prefix` Compiled from SVN sources as of 21/05/05, although the same has happened with all the release tarballs I've tried so far (1.2 to 1.2.4). Well, you must ensure that only one copy of amaroK is installed, one of these commands may help: $ locate amarokapp $ find / -name amarokapp If you installed an amaroK package from some distro, uninstall that before. After you configure, and when you make, can you see "-g3" in the middle of the lots of text you see there? (Just use sth to search for it.) The only amarokapp is the one I am compiling. "-g3" does appear in the output from the make process. And if you type amarokapp in a console you don't see anything? I get the following output. "end from FAM..." appears when I quit. [nah@cosy1 ~]$ amarokapp Link points to "/tmp/ksocket-nah" Link points to "/tmp/kde-nah" kbuildsycoca running... QObject::connect: Cannot connect Engine::Base::statusText( const QString& ) to (null)::shortMessage( const QString& ) QObject::connect: Cannot connect Engine::Base::infoMessage( const QString& ) to (null)::longMessage( const QString& ) QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow Caps negotiation succeeded with 44100 Hz @ 2 channels STARTUP end from FAM server connection Failed to write bytes to socket 11 Failed to write bytes to socket 11 Failed to write bytes to socket 11 [nah@cosy1 ~]$ Start the tool "kdebugdialog" and make sure that area 0 is checked. Area 0 (generic) is checked, so are all the amarok boxes. On Saturday 28 May 2005 10:37, Nick Hawes wrote:
> ------- Area 0 (generic) is checked, so are all the amarok boxes.
Alright, running out of ideas. Probably your kdelibs itself is built with
NDEBUG enabled, which suppresses all debug output.
SOrry for being such a pain, and thanks for the help. My kdelibs is from a Fedora Core 3 rpm. I will try compiling it from source when I get a chance. Redhat patches kdelibs to output no debug info by default, but doesn't patch kdebugdialog accordingly, so it is broken. Please try to create (or modify) the file ~/.kde/share/config/kdebugrc to have the following two lines in it: [0] InfoOutput=2 I don't use FC, so I couldn't test, but it should enable debug output. |