• 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: Using watchpoints... (was Re: Possible GCC Bug?)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using watchpoints... (was Re: Possible GCC Bug?)


  • Subject: Re: Using watchpoints... (was Re: Possible GCC Bug?)
  • From: "B.J. Buchalter" <email@hidden>
  • Date: Wed, 9 Apr 2008 20:29:55 -0400


On Apr 9, 2008, at 8:00 PM, Jim Ingham wrote:


Make sense. I am not on 3.1 yet, so I *don't* think I have seen that behavior yet. But the problem I was talking about has nothing to do with the location issue. Rather it has to do with the fact that Xcode sends gbd an expression that makes gdb barf and the watchpoint is not set at all, which is why you often have to take a trip to the debugger console....



I see. There's one bug we fixed recently that would cause the expression the UI makes up to be incorrect. In that case, you had to have a pointer to an object whose static type was different from its dynamic type, and the sub-element you were pointing to had to belong to the dynamic part of the type of the object, not the static part. We weren't up-casting to the dynamic type when we put the expression together.

That sounds like it.

the error message said something about invalid expression, and the quoted part of the expression started with a close paren )



But other than that, I don't have Radars on any other problems with generating valid expressions out of the local variable tree in Xcode.


Sorry -- did not file a radar.

Can you turn on the Xcode/gdb log (in Xcode 3.0 you do this in the Debugging Pref Pane) and then generate the watch expression through the UI that "makes gdb barf" and then file a bug with that log and the correct expression you were typing in the console (or just type in in the console, that will make its way into the log), and maybe we can figure out why the UI isn't cons-ing up the correct expression?

Yes -- I will try to find the location again and file a bug.

Best regards,

B.J. Buchalter
Metric Halo
http://www.mhlabs.com
	


_______________________________________________ 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: 
 >Possible GCC Bug? (From: "Greg Knight" <email@hidden>)
 >Re: Possible GCC Bug? (From: Jack Repenning <email@hidden>)
 >Re: Possible GCC Bug? (From: "B.J. Buchalter" <email@hidden>)
 >Re: Possible GCC Bug? (From: Jack Repenning <email@hidden>)
 >Re: Possible GCC Bug? (From: Jens Ayton <email@hidden>)
 >RE: Possible GCC Bug? (From: "Greg Knight" <email@hidden>)
 >Re: Possible GCC Bug? (From: "B.J. Buchalter" <email@hidden>)
 >Re: Possible GCC Bug? (From: Jack Repenning <email@hidden>)
 >Re: Possible GCC Bug? (From: "B.J. Buchalter" <email@hidden>)
 >Using watchpoints... (was Re: Possible GCC Bug?) (From: Jim Ingham <email@hidden>)
 >Re: Using watchpoints... (was Re: Possible GCC Bug?) (From: "B.J. Buchalter" <email@hidden>)
 >Re: Using watchpoints... (was Re: Possible GCC Bug?) (From: Jim Ingham <email@hidden>)

  • Prev by Date: Re: Using watchpoints... (was Re: Possible GCC Bug?)
  • Next by Date: Re: Linking troubles with Lua
  • Previous by thread: Re: Using watchpoints... (was Re: Possible GCC Bug?)
  • Next by thread: Re: Possible GCC Bug?
  • Index(es):
    • Date
    • Thread