[Psi-devel] [BUG] Unusable Psi

[Michał Jazłowiecki]

textshell wrote:

> what exactly do you mean by gdb froze? If you type continue psi will
> not take any input, until your programm is halted again, either by
> pressing ctrl-c in the gdb window or by some crash/breakpoint.

Let's suppose that Psi's PID is 3856:

(gdb) attach 3856
Attaching to process 3856
[Switching to thread 3856.0x60c]
(gdb) continue
Continuing.

My question is: Should gdb return to its (gdb) prompt now, or it will 
wait for something to break into debugger? Ctrl-C doesn't seem to work 
(no response) and Ctrl-Break terminates gdb.

> the other way is to start psi from gdb: (approx like this)
> $ gdb psi
> (gdb) start
> [now get psi to the hang]
> <ctrl>-C
> (gdb) bt
> [stack trace follows]

This one works for me, although it's not "start" but "run". And Ctrl-C 
still doesn't work. Maybe this has something to do that my gdb is 
version 5.2.1 and the newest available for Unices is 6.6 :/


Anyway, something has changed over the time as Psi does not freeze 
anymore while connecting to chrome.pl. And I didn't change anything in 
Psi options nor did I recompile Psi. I will retry the procedure once Psi 
starts freezing again.


Thanks for the info about gdb,


-- 
Michał Jazłowiecki (michalj)
Psi Forum & Wiki Moderator :: Psi-Daisy Author