Summary: | Kdevelop hanged afer run using CLI | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Marek Witkowski <marek.witkowski.priv> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | REPORTED --- | ||
Severity: | crash | CC: | igorkuo |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | kdevelop process with GDB and printing the backtrace of all threads |
Description
Marek Witkowski
2023-03-30 18:23:34 UTC
Try opening another session or a new session: `kdevelop -n test-session`. The backtrace is too short. Have you tried attaching to the hanging kdevelop process with GDB and printing the backtrace of all threads? gdb -batch -ex "thread apply all bt" -ex "quit" -p 12345 > /some/path/hanging-kdevelop.bt ("12345" in the command stands for the hanging kdevelop process ID) If you get the `ptrace: Operation not permitted.` error, run the following command before repeating the gdb command: echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope (you can revert the configuration change with `echo 1 | sudo tee /proc/sys/kernel/yama/ptrace_scope`) Created attachment 157744 [details]
kdevelop process with GDB and printing the backtrace of all threads
kdevelop process with GDB and printing the backtrace of all threads
after: gdb -batch -ex "thread apply all bt" -ex "quit" -p 12345 > /some/path/hanging-kdevelop.bt
(In reply to Igor Kushnir from comment #1) > Try opening another session or a new session: `kdevelop -n test-session`. > > The backtrace is too short. Have you tried attaching to the hanging kdevelop > process with GDB and printing the backtrace of all threads? > gdb -batch -ex "thread apply all bt" -ex "quit" -p 12345 > > /some/path/hanging-kdevelop.bt > ("12345" in the command stands for the hanging kdevelop process ID) > If you get the `ptrace: Operation not permitted.` error, run the following > command before repeating the gdb command: > echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope > (you can revert the configuration change with `echo 1 | sudo tee > /proc/sys/kernel/yama/ptrace_scope`) After `kdevelop -n test-session` works fine. (In reply to Marek Witkowski from comment #2) > Created attachment 157744 [details] > kdevelop process with GDB and printing the backtrace of all threads QTimerInfoList::unregisterTimer(int) is unlikely to hang. Could you run the gdb -batch command several times on a single hanging kdevelop process to compare backtraces and maybe figure out where the process is stuck? |