• 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: [Q] Breakpoint problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Q] Breakpoint problem


  • Subject: Re: [Q] Breakpoint problem
  • From: Michael Miller <email@hidden>
  • Date: Mon, 21 Mar 2011 13:03:19 -0400

I know it was a little off-topic--I was simply adding to what Scott said.

Along the same lines though, you could try using GDB to set the breakpoint and see if you fare any better.  Not an ideal solution, but might solve some of your problems.  Syntax is: "break filename:line#" (or "b filename:line#" for short).  It's worth seeing where GDB thinks Xcode set the breakpoint.  Xcode in this case is just wrapping GDB so it's really up to GDB whether it breaks there or not.

Michael Miller

On Mar 21, 2011, at 12:58 PM, Howard Moon wrote:

> There was no phantom breakpoint.  No matter where I put the try/catch, it would break on whatever line followed the end of the catch, as if the whole catch block were optimized out. Changing the code in the catch block to a function call to some meaningless function lets me break inside that function instead (although that's just an annoying workaround, not a real fix).
>
> Thanks,
> 	Howard
>
> On Mar 21, 2011, at 9:53 AM, Michael Miller wrote:
>
>> If you're using GDB, you can also open the console and type "info break" to list all the breakpoints and their breakpoint ID numbers.  To delete a specific breakpoint, type "delete break #".  "delete break" will delete every breakpoint.     All you need to do is find the breakpoint that's Xcode failed to really delete and get rid of that one.  (You can shorten these as well--"i b," "d b #," and "d b" will work equally well).
>>
>> Michael Miller
>>
>> On Mar 21, 2011, at 12:46 PM, Scott Ribe wrote:
>>
>>> I've seen it sometimes where there's a "phantom" breakpoint that Xcode won't display, but breaks on. In that case, opening the breakpoints window and deleting everything fixes it.
>>>
>>> --
>>> Scott Ribe
>>> email@hidden
>>> http://www.elevated-dev.com/
>>> (303) 722-0567 voice
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>
>
> _______________________________________________
> 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
>

 _______________________________________________
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: 
 >[Q] Breakpoint problem (From: JongAm Park <email@hidden>)
 >Re: [Q] Breakpoint problem (From: Scott Ribe <email@hidden>)
 >Re: [Q] Breakpoint problem (From: Michael Miller <email@hidden>)
 >Re: [Q] Breakpoint problem (From: Howard Moon <email@hidden>)

  • Prev by Date: Re: [Q] Breakpoint problem
  • Next by Date: Re: from symbol name to full documentation in Xcode 4
  • Previous by thread: Re: [Q] Breakpoint problem
  • Next by thread: Re: [Q] Breakpoint problem
  • Index(es):
    • Date
    • Thread