• 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: Xcode 3.2 -- Two more bugs??
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode 3.2 -- Two more bugs??


  • Subject: Re: Xcode 3.2 -- Two more bugs??
  • From: Jean-Daniel Dupas <email@hidden>
  • Date: Mon, 31 Aug 2009 21:32:19 +0200

OK, so it wasn't GBD on Leopard.
I though it uses the same trick on Leopard because I encounter some issues while playing with mach exception. I noticed that when I launched an application from Xcode, something was swapping my application exception port just like GDB used to do.


- Jean-Daniel

Le 31 août 2009 à 21:08, Jim Ingham a écrit :

Exactly. In Xcode 3.1, Xcode would catch the crash and then pass the exception to gdb, but that was a lossy process. In 3.2, we let gdb run the program, and that way we can tell exactly what happened when the program dies. But that means if you have a program that doesn't run under the debugger, you now need to uncheck the "Auto- attach debugger on crash" to restore the old behavior.

Jim

On Aug 31, 2009, at 12:02 PM, Jens Alfke wrote:


On Aug 31, 2009, at 11:51 AM, Jim Ingham wrote:

No it doesn't mean that. When Xcode is "running" without setting any breakpoints, there are a lot of the pieces of information gdb normally gathers that we know it doesn't need. So we cooked up some startup settings that tell gdb not to notice things like shared library loading and not to read any symbol information at all, etc. If you only need to use gdb as a program launcher not a debugger, it doesn't add much overhead. It's only when you want to do things like look at symbols or set breakpoints that you start to pay for having gdb around.

I think I understand now. So is this mode new in 3.2? I just tried running an app in Xcode 3.1 in the "Breakpoints disabled" mode, and there is no gdb process running at all.


So far Xcode is by far my top reason for wanting to upgrade to 10.6.

—Jens

_______________________________________________ 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: 
 >Xcode 3.2 -- Two more bugs?? (From: "McLaughlin, Michael P." <email@hidden>)
 >Re: Xcode 3.2 -- Two more bugs?? (From: Joar Wingfors <email@hidden>)
 >Re: Xcode 3.2 -- Two more bugs?? (From: Jim Ingham <email@hidden>)
 >Re: Xcode 3.2 -- Two more bugs?? (From: Jens Alfke <email@hidden>)
 >Re: Xcode 3.2 -- Two more bugs?? (From: Jim Ingham <email@hidden>)
 >Re: Xcode 3.2 -- Two more bugs?? (From: Jens Alfke <email@hidden>)
 >Re: Xcode 3.2 -- Two more bugs?? (From: Jim Ingham <email@hidden>)

  • Prev by Date: Re: custom executable fails to launch
  • Next by Date: Re: custom executable fails to launch
  • Previous by thread: Re: Xcode 3.2 -- Two more bugs??
  • Next by thread: Preccompiled header compatibility
  • Index(es):
    • Date
    • Thread