• 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
problem with source code debugging for dynamically linked libraries
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

problem with source code debugging for dynamically linked libraries


  • Subject: problem with source code debugging for dynamically linked libraries
  • From: Borghesi <email@hidden>
  • Date: Fri, 28 Nov 2003 17:01:33 +0100

The whole thing is a C program loading dynamically several shared
libraries (compiled as bundles) and everything is compiled with the
debugging option.

This is what happens:
  - we launch the C program (Target of type Standard Tool)
  - this program links dynamically several shared libraries using
NSLinkModule()

These are the symptoms:
  - we can't set breakpoints inside of the code of the shared libraries
using the arrows of the GUI
  - if we set a symbolic breakpoint (using a function name) the debugger
stops, but the we don't have access to the source or any state
  - the function name in the display of the C function stack is gray
  - using next in the debugger (or the "Step Over" button)we have the
following error message:
       "Single stepping until exit from function osc_set_phase, which
has no line number information."

Everything worked well with ProjectBuilder on Jaguar.

Any hints or experiences?

Regards
    Riccardo
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: problem with source code debugging for dynamically linked libraries
      • From: String <email@hidden>
  • Prev by Date: Re: XCode or CodeWarrior 9
  • Next by Date: Re: problem with source code debugging for dynamically linked libraries
  • Previous by thread: Re: Missing CHUD.kext?
  • Next by thread: Re: problem with source code debugging for dynamically linked libraries
  • Index(es):
    • Date
    • Thread