Lists

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

Inlining doesn't lose stack trace anymore?

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

Inlining doesn't lose stack trace anymore?

Subject: Inlining doesn't lose stack trace anymore?
From: "Theodore H. Smith" <email@hidden>
Date: Fri, 21 Mar 2008 00:55:38 +0000

Hi everyone, just a silly quick question.

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?

I remember the day, when a crash in an inlined function would mean you don't get that inlined function's name.

Or is it that my function isn't really inlined. :( So has gcc improved, or is my function not really inlined?

--
http://elfdata.com/plugin/
"String processing, done right"


_______________________________________________
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: Inlining doesn't lose stack trace anymore?
From: Jim Ingham <email@hidden>
Re: Inlining doesn't lose stack trace anymore?
From: David Dunham <email@hidden>


Prev by Date:
Wrong Frameworks Build Configuration Copied to App Pkg

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

Previous by thread:
Re: Wrong Frameworks Build Configuration Copied to App Pkg

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

Index(es):

Date
Thread