Registered Member
|
recompiled as said with -g3 and got this:
|
Registered Member
|
Not only plasmashell doesn't work but I have no display at all.
|
Administrator
|
If you start plasmashell directly from a terminal, do you get any output which may indicate what the problem is? (Hopefully it will be aware it has entered into a loop)
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Tried plasmashell --sync , but this option wasn't accepted by the command. however it exists a -sync but is not documented and asks for an argument.
|
Registered Member
|
Nevertheless a few commands such as kate, konsole and surprisingly kdevelop work from kde4 if proper variables have been set.
|
Administrator
|
The --sync option is not necessary - just start it as a simple "plasmashell".
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
I did that, but with or without --sync, with or without gdb backtrace, still no clue about why plasmashell loops like a crazy horse
|
|
in gdb, "info threads" will print a list of all threads. eg. "thread 2" would then change to thread 2 and issuing "bt" there will print the backtrace for that thread.
you can this way navigate through all threads and obtain their stacks. |
Registered Member
|
It would be simpler to get the pid of the "mad" thread, but I don't know which tool to use i.e. to get the cpu times of threads related to a specific process, if I can do that with top, pstree or ksysguard or another tool. I tried all of them but none gave me the right answer.
|
|
it's hopefully the one that is not dormant
to profile an appliction you best run it in "valgrind --tool callgrind" (which unlike eg. gprof needs no special compilation flags) |
Registered Member
|
No, I just need to know the pid of the faulty thread, not the pid of the parent process (ppid) as displayed by top
|
Registered users: bartoloni, Bing [Bot], Google [Bot], Yahoo [Bot]