Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Inlining doesn't lose stack trace anymore?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Inlining doesn't lose stack trace anymore?

Subject: Re: Inlining doesn't lose stack trace anymore?
From: David Dunham <email@hidden>
Date: Thu, 20 Mar 2008 18:37:52 -0700

So... I was doing some testing on some code of mine. Its a code to do with fuzzy string searches.

And... I was debugging it. The app crashed. MacOSX helpfully gave me the stack trace. The crash was in an inlined function.

Is that possible? Can the function be inlined, AND I get my function name? Is gcc that advanced now?

If you're debugging it, there's a good chance you're using a debug build. And there's a good chance you have

GCC_OPTIMIZATION_LEVEL = 0

set for your target

David Dunham
Voice/Fax: 206 783 7404             http://www.pensee.com/dunham/
Imagination is more important than knowledge. -- Albert Einstein

_______________________________________________
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:  
  >Inlining doesn't lose stack trace anymore? (From: "Theodore H. Smith" <email@hidden>)




Prev by Date:
Inlining doesn't lose stack trace anymore?

Next by Date:
Re: Inlining doesn't lose stack trace anymore?

Previous by thread:
Inlining doesn't lose stack trace anymore?

Next by thread:
Re: Inlining doesn't lose stack trace anymore?

Index(es):

Date
Thread