Hi, I'm wondering if anyone else has experienced this problem with idb:
if the debugger is invoked via the command "idb ./mycode", the idb GUI
comes up and I do my debugging...no problem. When done, I select "Exit"
under "File" in the menu bar. The GUI then exits, but control is not
returned to the window from which it was launched, and the window is
locked. "Ctrl-C" does not release it, and if I open another window and
issue "ps -u myusername", I see three processes related to idb still
running: idb, java, and "iidb ". I have to manually
kill each of these from the second window before I can regain control
of the first. This becomes irritating after a few sessions.
there a way to have these "zombie" processes go away without this
annoyance? Is there a better way to launch idb so this is not an
issue? Thanks in advance for your advice!