On Friday, June 10, 2016 12:45:28 AM, Alexander Potashev, an eminent
manifestation of divinity, wrote:
> A more direct way of debugging hang-ups is to run the program is
> debugger and see the stacktrace. Next time Amarok starts hanging up
> often on your computer,
> 1. Run amarok in GDB:
> gdb amarok
> (wait for GDB to load...)
> run --nofork
> 2. When the UI hangs up, go to the terminal where you started GDB and
> press Ctrl+C to "pause" the amarok process.
> 3. See the stacktrace:
> bt
> 4. Or even better, see the stacktraces for all threads:
> thread apply all bt
>
> A stacktrace will probably show where in the code it has "hung up".
this won't help, because it isn't "running and then hangs up", it's "not
running, and won't start"... i click the icon, or type "amarok" and hit enter,
it looks like it's going to start, and then it doesn't...
only now it does, which is, ultimately, the goal, but doesn't help me figure
out what has gone wrong. 8/
--
namaste
salamandir
salaman...@hybridelephant.com
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?
() ascii ribbon campaign - against html e-mail
/\ - against proprietary attachments
--
Great minds discuss ideas, average minds discuss events, small minds discuss
people.
-- Eleanor Roosevelt
_______________________________________________
Amarok mailing list
Amarok@kde.org
https://mail.kde.org/mailman/listinfo/amarok
