• 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
auto-gdb
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

auto-gdb


  • Subject: auto-gdb
  • From: Jack Nutting <email@hidden>
  • Date: Mon, 8 Mar 2010 11:25:26 +0100

Prior to Xcode 3.2, while running an app from within Xcode (with the
"Run" command, not just the "Debug" command), any crash in the app
would magically stop on kill() in gdb, letting me examine things just
as if I had run it through the debugger in the first place.  I know
this is the way it worked at least in 3.1, but don't know for how long
it's been that way.

Anyway, that behavior seems to be gone in 3.2, and any app that
crashes just dumps unceremoniously back to Xcode, with no output in
the Xcode console log or anything.  Is there any way to get the old
behavior back, besides just always running through gdb?

--
// jack
// http://nuthole.com
// http://learncocoa.org
 _______________________________________________
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: auto-gdb
      • From: Ken Thomases <email@hidden>
  • Prev by Date: Re: Xcode-users Digest, Vol 6, Issue 519
  • Next by Date: Adding explicit dependency on Info.plist file for standalone executables
  • Previous by thread: Re: Xcode-users Digest, Vol 6, Issue 519
  • Next by thread: Re: auto-gdb
  • Index(es):
    • Date
    • Thread