data formatters unreliable?
data formatters unreliable?
- Subject: data formatters unreliable?
- From: Sam Deane <email@hidden>
- Date: Mon, 4 Dec 2006 14:49:34 +0000
I've been trying to use some custom summary formats and data
formatters to make my debugging experience a bit saner. Potentially,
this is a very handy feature of XCode, but instead it seems to be
driving me further towards the edge!
I have a formatter plugin based on the wchardataformatter sample
code. When I test this plugin using the small test program provided,
it works fine.
When I test it in my own code (spread over 3 projects incidentally -
an application linked to two static libraries), and look at wchar_t*
strings, it _sometimes_ works, and sometimes doesn't - with no
obvious explanation as to why.
When I test it in my own code using custom types derived from wchar_t
and wchar_t*, I can't get it to work at all, although I did
tantalisingly get it to work once!
Are there any known issues with this stuff? Does it work reliably for
everyone else? Are there any project settings that need to be given
certain values - e.g. using DWARF instead of Stabs, or turning Fix &
Continue off, or something similarly obscure.
I occasionally get "warning: Attempt to use a type name as an
expression." appearing in the gdb debug console.
I'm using XCode 2.4 on intel macs (a MacBookPro and a MacPro) using
10.4.8.
Yours in frustration...
_______________________________________________
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