• 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
Re: Inline functions get debugger confused about source files
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Inline functions get debugger confused about source files


  • Subject: Re: Inline functions get debugger confused about source files
  • From: Rua Haszard Morris <email@hidden>
  • Date: Wed, 18 Jul 2007 12:17:09 +1200

I see that issue all the time, especially with C++/classes code, where you will step into a header file for certain breakpoints, and my workaround is to find a way to debug using a breakpoint in a different place :(

(It would have been nice to hear an acknowledgement of the bug in response to your posting, so here's mine ...)

My advice is if an unmentionable unreleased product works for you then go with it for your debugging sessions :)

On 18/07/2007, at 12:08 PM, Jason Molenda wrote:

Dave, Leopard is under NDA and should not be discussed on this public mailing list. Please feel free to ask questions regarding Leopard on email@hidden.

Thanks

Jason

On Jul 17, 2007, at 3:36 PM, Dave Camp wrote:

I'm having the same problems referenced here <http:// lists.apple.com/archives/xcode-users/2005/Jul/msg00178.html> and here <http://lists.apple.com/archives/xcode-users/2006/Jan/ msg01147.html> where the linker strips off too much debugger information and gdb displays a header file instead of the source I want to debug.

This bug is making it virtually impossible to debug a Windows application I'm porting. The suggestion of -fno-inline does not seem to help.

Are there any known workarounds for this on Tiger?

I have noticed that when I hit the problem on Tiger, the same code on Leopard is debuggable (gdb shows the correct source). Am I just getting lucky or is the bug fixed in a newer version of the linker? I am not opposed to switching to the seed release if thats the only way I can debug my code. :-)

Thanks,
Dave
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com


This email sent to email@hidden

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40adinstruments.com


This email sent to email@hidden

_______________________________________________ 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: Inline functions get debugger confused about source files
      • From: Alastair Houghton <email@hidden>
References: 
 >Inline functions get debugger confused about source files (From: Dave Camp <email@hidden>)
 >Re: Inline functions get debugger confused about source files (From: Jason Molenda <email@hidden>)

  • Prev by Date: Re: Inline functions get debugger confused about source files
  • Next by Date: Re: Inline functions get debugger confused about source files
  • Previous by thread: Re: Inline functions get debugger confused about source files
  • Next by thread: Re: Inline functions get debugger confused about source files
  • Index(es):
    • Date
    • Thread