Re: Tracing into libraries
Re: Tracing into libraries
- Subject: Re: Tracing into libraries
- From: Chris Espinosa <email@hidden>
- Date: Mon, 19 Sep 2005 21:40:56 -0700
On Sep 19, 2005, at 3:42 PM, Mark Wagner wrote:
I've got an application that consists of a single source file that
does almost nothing, and a half-dozen statically-linked libraries that
contain 99.999% of the application code. Obviously, when I'm
debugging this application, I need to be able to trace execution into
the libraries. However, I can't. How can I tell if the libraries are
built with debugging information, and if they aren't, how can I tell
XCode to include the information when building them?
Are the static libraries built as part of the same project as the application, or by different projects?
Does your app link with the static libraries from an intermediate build folder or some "final destination" like /usr/local/lib?
If you use nm -j /path/to/myStaticLib.a, do you see a lot of entries starting with "t" (local symbols) as well as with "T" (exported symbols)?
When you say "[you] can't," please explain what actually happens. Oh, and please: mention the version of Xcode and version of gcc you're using.
What I recommend is adding
-t to your application's "Other Linker Flags", rebuild the app, and reply with the "Ld" line and its diagnostic output.
Chris
_______________________________________________
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