mi_cmd_exec_interrupt: inferior not executing
mi_cmd_exec_interrupt: inferior not executing
- Subject: mi_cmd_exec_interrupt: inferior not executing
- From: Brad Oliver <email@hidden>
- Date: Tue, 23 Jan 2007 21:40:26 -0700
Frequently when stepping through C++ code, the debugger will appear
to stall or lock up. If I click on the pause button when this
happens, I get the following message:
Error from Debugger: mi_cmd_exec_interrupt: Inferior not executing.
When this happens, I know that I'm royally screwed and have to kill
my app and start a new debugging session. I can open up the debugger
console, but entering any command at the (gdb) prompt seems to result
in a big fat nothing.
Anyone know what is going on and better yet - how I can avoid it?
There's truly nothing worse that being neck-deep into debugging a
problem and have the debugger crap out on you, forcing you to start
all over.
--
Brad Oliver
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden