Re: Debugging dreams?
Re: Debugging dreams?
- Subject: Re: Debugging dreams?
- From: Alexander Heusel <email@hidden>
- Date: Wed, 7 Jun 2006 14:42:09 +0200
I think I see what you're saying, and you're right, that would
work. The reason I was hoping to write something that plugs into
XCode is that my current system requires me to make changes to my
code. This is problematic for two reasons:
1) I'm not seeing what my code is doing, I'm seeing what my code +
my update function is doing. This is problematic because if my
update function has a bug in it, then I need to debug that as
well. In addition, it may change the state of the machine in a
manner that is different than what would happen if the update code
isn't there (currently, I use macros everywhere, which I define as
nothing when I don't want them)
2) I have to manually go through and instrument my code everywhere
I see a variable update. If I miss a single location, then what I
see, and what I think I see are two different things.
For these reasons, I'd rather use something provided by XCode. I
know that the XCode team have a much better understanding of
instrumenting code than I do, and could provide a much cleaner
interface. Also, if I ran into bugs, I would have a greater level
of trust that it was a real problem, and not a potential problem in
my debug code. In short, I have reasons for wishing to use XCode
as my data source.
Thanks,
Cem Karan
Hmm, I think any solution which would work without
instrumenting your code would require to patch gdb
itself. Anyway, Apple is working on visual debugging.
It is already there in the current Xcode. However in
the moment it only supports only class-trees as far as
I know. And hey probably they deliver your idea
with a WWDC - release of Xcode, who knows?
Regards,
Alexander
_______________________________________________
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