• 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: Thread ID in debugger window versus console
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Thread ID in debugger window versus console


  • Subject: Re: Thread ID in debugger window versus console
  • From: Michael Crawford <email@hidden>
  • Date: Mon, 2 Feb 2009 20:15:14 -0800

On Mon, Feb 2, 2009 at 5:45 PM, Peter Duniho <email@hidden> wrote:
> And barring that, is there some way in the debugger, once an exception has
> occurred (exception thrown, fault, etc.), to at least show the thread where
> the exception happened?

Place a breakpoint on the exception's constructor.  If you don't know
for sure the extension type, placing a breakpoint on the
std::exception base class constructor might catch it, if you are so
fortunate that your exception is a subclass of it.

Mike
--
Michael David Crawford
mdcrawford at gmail dot com

   I'm looking for a job in Silicon Valley:
     http://www.goingware.com/resume/cover-letter.html
 _______________________________________________
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

  • Follow-Ups:
    • Re: Thread ID in debugger window versus console
      • From: David Dunham <email@hidden>
References: 
 >Thread ID in debugger window versus console (From: Peter Duniho <email@hidden>)

  • Prev by Date: Re: Thread ID in debugger window versus console
  • Next by Date: Re: Thread ID in debugger window versus console
  • Previous by thread: Re: Thread ID in debugger window versus console
  • Next by thread: Re: Thread ID in debugger window versus console
  • Index(es):
    • Date
    • Thread