• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Random Crash While Debugging (was Re: mi_cmd_exec_interrupt: inferior not executing)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Random Crash While Debugging (was Re: mi_cmd_exec_interrupt: inferior not executing)


  • Subject: Re: Random Crash While Debugging (was Re: mi_cmd_exec_interrupt: inferior not executing)
  • From: Doug Hill <email@hidden>
  • Date: Wed, 31 Jan 2007 11:52:32 -0800

Brad,

I have been getting the exact same errors that you experience. In my case, looking through the assembly I noticed code-gen errors. This had to do with problems compiling Boost using the Objective-C++ compiler. Your problem may be compiler errors which lead to gdb crashing/failing. If you can make a reproduceable case, I would log a bug with Apple using Bug Reporter and have them look at it.

doug

Jeremy Sagan wrote:
I am frequently experiencing a very similar problem. After debugging for a while XCode will randomly stop with "Single stepping until exit from function _start, which has no line number information.Program received signal: "EXC_BAD_ACCESS". This happens at random times and at random places in the code and never happens when XCode is out of the picture. Brad writes "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." This is at least true in an XCode debugging context.

Jeremy



On Jan 23, 2007, at 11:40 PM, Brad Oliver wrote:

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
References: 
 >mi_cmd_exec_interrupt: inferior not executing (From: Brad Oliver <email@hidden>)
 >Random Crash While Debugging (was Re: mi_cmd_exec_interrupt: inferior not executing) (From: Jeremy Sagan <email@hidden>)

  • Prev by Date: Re: Auto-save of .h files on build?
  • Next by Date: Re[2]: Turning off 'deleting 'VOID*' is undefined' error
  • Previous by thread: Random Crash While Debugging (was Re: mi_cmd_exec_interrupt: inferior not executing)
  • Next by thread: Re: Using ANT and seeing output
  • Index(es):
    • Date
    • Thread