• 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: Stopping on Debugger()
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Stopping on Debugger()


  • Subject: Re: Stopping on Debugger()
  • From: tyler <email@hidden>
  • Date: Sat, 12 Jan 2008 22:56:58 -0800

raise( SIGTRAP );

though it stops down in raise so you have to step out a couple of times to get where you want to be.

raise( SIGINT ); also works but that aborts your app and you cannot continue.

info signals

in gdb console in Xcode has other interesting signals info, btw.

On Nov 27, 2007, at 10:56 AM, David Dunham wrote:

I've got an assert function that can call Debugger(). In the old days, this would drop into a debugger. Doesn't seem to any more (Xcode 3.0).

Is there a way to do so? Or do I just set a breakpoint at Debugger (which seems oddly ugly).


David Dunham Macintosh Game Developer GameHouse Studios +1 206 926 5722 www.gamehouse.com "They said it couldn't be done but sometimes it doesn't work out that way." -- Casey Stengel

_______________________________________________
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
  • Prev by Date: Re: Linker shows "has different visibility" warning
  • Next by Date: GDB Crash
  • Previous by thread: Re: Linker shows "has different visibility" warning (2nd)
  • Next by thread: GDB Crash
  • Index(es):
    • Date
    • Thread