https://bugzilla.suse.com/show_bug.cgi?id=1199425 https://bugzilla.suse.com/show_bug.cgi?id=1199425#c6 --- Comment #6 from Matthias Brugger --- (In reply to Freek de Kruijf from comment #3)

I did run into the same situation. I tried to connect to both the process in the strange state as to a process that simply hangs. Because of my ignorance in using gdb I could not gather any information. I tried to get access using "gdb ./SBFspot <process-ID>", but the few last times I used it, I did not get a prompt from gdb and needed to kill the terminal window or via another window kill the gdb command. If I recall properly, when I tried it the first time I did get a prompt, but gdb commends I gave did not return what I expected. Maybe I expected the wrong things, which I discarded.

Anyway I now have to wait for the hanging process again. I implemented in the script that when the BT Signal gives 39.6%, I do not continue with calling the program each 5 minutes. I get an e-mail when this situation occurs, so I can control what happens next, when I run the program again with it own debugging and when it gets stuck I will try to use gdb and report whatever the reaction is.

In case you have further suggestions, please send these.

You will need to load the debug information for your program. Can you have a look if you can compile the tool with debug information enabled? After that you should be able to connect to the running process and see the backtrace with 'bt'. -- You are receiving this mail because: You are the assignee for the bug.