• 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: Getting poor stack traces
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Getting poor stack traces


  • Subject: Re: Getting poor stack traces
  • From: Jens Alfke <email@hidden>
  • Date: Tue, 30 Jul 2013 14:36:32 -0700


On Jul 30, 2013, at 2:13 PM, Michael Crawford <email@hidden> wrote:

In your Xcode project settings, do you enable Stack Frames in your
machine code generation?  I don't know what the actual setting will be
called in the current Xcode, but most compilers permit one to enable
or disable them.

Um, I don't recall seeing any compiler settings for that since the days of CodeWarrior and the classic OS. I suspect that either the OS X ABI makes the distinction unnecessary, or that the system code that generates backtraces is smart enough to detect stack frames even without help from the compiler.

—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

References: 
 >Getting poor stack traces (From: Rick Mann <email@hidden>)
 >Re: Getting poor stack traces (From: Michael Crawford <email@hidden>)

  • Prev by Date: Re: Getting poor stack traces
  • Next by Date: Re: I have a 0-day exploit, but don't want to tell you what it is
  • Previous by thread: Re: Getting poor stack traces
  • Next by thread: Symbolicating arbitrary crash logs
  • Index(es):
    • Date
    • Thread