• 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: Debugger has exited due to signal 11 (SIGSEGV)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Debugger has exited due to signal 11 (SIGSEGV)


  • Subject: Re: Debugger has exited due to signal 11 (SIGSEGV)
  • From: Paul Berkowitz <email@hidden>
  • Date: Wed, 05 Jul 2006 10:05:27 +0100
  • Thread-topic: Debugger has exited due to signal 11 (SIGSEGV)

Title: Re: Debugger has exited due to signal 11 (SIGSEGV)
On 7/5/06 12:27 AM, "Peter CK" <email@hidden> wrote:

why it happend. I'm still using Xcode 2.2, but I'll have to wait for my company before upgrading. If it makes a difference between v2.2 and v2.3, then it's abviously Xcodes fault.

No, you didn't understand what you were being told. Xcode 2.3 lets you use DWARF debugging instead of STABS (all that is available in 2.2). So if the problem is with gdb under STABS you can avoid the issue by using DWARF in 2.3.

--
Paul Berkowitz
 _______________________________________________
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: 
 >Re: Debugger has exited due to signal 11 (SIGSEGV) (From: "Peter CK" <email@hidden>)

  • Prev by Date: Build Error third time onward
  • Next by Date: Re: Debugger has exited due to signal 11 (SIGSEGV)
  • Previous by thread: Re: Debugger has exited due to signal 11 (SIGSEGV)
  • Next by thread: Re: Debugger has exited due to signal 11 (SIGSEGV)
  • Index(es):
    • Date
    • Thread