• 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
Tracing into libraries
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Tracing into libraries


  • Subject: Tracing into libraries
  • From: Mark Wagner <email@hidden>
  • Date: Mon, 19 Sep 2005 15:42:54 -0700

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?

Thanks,
Mark Wagner
 _______________________________________________
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: Tracing into libraries
      • From: Chris Espinosa <email@hidden>
  • Prev by Date: Re: Re: Disabling creation of Development / Deployment / Debug folders in Xcode 2.1 builds
  • Next by Date: Resource forks
  • Previous by thread: Re: Re: Disabling creation of Development / Deployment / Debug folders in Xcode 2.1 builds
  • Next by thread: Re: Tracing into libraries
  • Index(es):
    • Date
    • Thread