• 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: Debugger confused about line numbers
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Debugger confused about line numbers


  • Subject: Re: Debugger confused about line numbers
  • From: Jim Ingham <email@hidden>
  • Date: Mon, 21 Mar 2005 10:27:07 -0800

If you put together a small project which shows the problems you are having then it would be great if you could file a bug and put that in it.

Otherwise, we are all just speculating...

Another couple of things you can do:

1) This is the standard Xcode Debugger debugging procedure:

1) Quit Xcode.
2) In Terminal, say:

$ defaults write com.apple.Xcode PBXGDBDebuggerLogToFile YES
$ defaults write com.apple.Xcode PBXGDBDebuggerLogFileName /tmp/ IncludeInBug.log


3) Restart Xcode, and exercise it to make it show the bad behavior.
4) Attach /tmp/IncludeInBug.log to the Radar.

Another interesting thing would be to see whether gdb & Xcode agree about your sources. After you have set your breakpoints, and run your program, interrupt it, open the Debugger console, and do:

(gdb) info break

Take some of the file:line specs that you get from gdb for the breakpoints, and do:

(gdb) list file:line

Do these match the file & line listings you get from Xcode? For instance, if you have \r\n or some other line ending that confuses Xcode, usually these don't confuse gdb. You could then back up in the gdb listings till you find the place where Xcode & gdb get back on track, and see if there is something funny in the file there.

Jim

On Mar 19, 2005, at 1:36 PM, Larry Campbell wrote:

On Mar 19, 2005, at 3:39 PM, carbonized wrote:


On Mar 19, 2005, at 11:36 AM, Tony Cate wrote:


I see this on a regular basis.


I see it periodically, but I found it's caused by uncompiled changes in the code. I've also seen it happen when I've had a second version of the code open that has break-points in it (debugger breaks on all the combined break-points).



This problem caused me no end of frustration until somebody pointed out that it might be caused by \r\n line endings. I cleaned up all of my files, and the problem disappeared.


Neither case applies to me. All my files are unique, and none contains \r (I checked with find, od, and grep).


- lc

_______________________________________________
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


_______________________________________________ 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
References: 
 >Re: Debugger confused about line numbers (From: Tony Cate <email@hidden>)
 >Re: Debugger confused about line numbers (From: carbonized <email@hidden>)
 >Re: Debugger confused about line numbers (From: Larry Campbell <email@hidden>)

  • Prev by Date: Re: Debugger confused about line numbers
  • Next by Date: XCode workflow question.
  • Previous by thread: Re: Debugger confused about line numbers
  • Next by thread: Re: Debugger confused about line numbers
  • Index(es):
    • Date
    • Thread