Code::Blocks Forums
Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: killerbot on January 10, 2006, 08:49:55 pm
-
In older svn builds I was able to see the value of wxString variables in the debugger/watches, I could see the content of the m_pchData, but now nothing is visible anymore ? Might this be a unicode effect ??
-
Might this be a unicode effect ??
Exactly.
-
any solution in the pipeline ?
-
any solution in the pipeline ?
Not yet but I 'm looking for one...
-
/nhc ??
http://blogs.msdn.com/joelpob/archive/2004/04/21/117664.aspx
-
x /nhc displays only a character. I 'm searching for a solution for strings...
-
x /nhc displays only a character. I 'm searching for a solution for strings...
This (http://www.skynet.ie/~caolan/TechTexts/GdbUnicodePrinting.html) could help?
Michael
-
Thanks for the link Michael, but it assumes that you have in *your* executable a couple of convenient functions. We want C::B to handle this automatically though.
But I 've found a workaround already. Testing its last bits now and committing soon :)
-
We want C::B to handle this automatically though.
Yes, I agree. Automatically would be preferably.
But I 've found a workaround already. Testing its last bits now and committing soon :)
Great :D.
Afer this document (http://sourceware.org/gdb/download/onlinedocs/gdb_9.html#SEC55):
More work inside GDB is needed to support multi-byte or variable-width character encodings, like the UTF-8 and UCS-2 encodings of Unicode.
I can just hope that this work will be done in a not-so-far future :).
Michael
-
Yes, I agree. Automatically would be preferably.
Hehe, we 're only aiming for the best ;)
OK committed.
Notes:
- New watch format defined: wxString
- Automatically recognizes watched variable's type and sets its format to wxString if appropriate. This means the user is required to do nothing. Just watch his wxString variable ;)
- Haven't tested with ANSI wxString. Could someone using the ANSI C::B test it?
- It doesn't work inside "Local variables" and "Function arguments" automatic watches. Only in user-added watches (no big deal, is it?).
:lol:
[attachment deleted by admin]
-
It doesn't work inside "Local variables" and "Function arguments" automatic watches. Only in
Is it a big job to get it also working in those cases ?
Well for the moment we'll just add them manually (manual automatically ;-) )
-
Is it a big job to get it also working in those cases ?
If it was easy I would have done it already.
On the other hand, I implemented it for tooltip evaluation too :)
-
Yeah but what happens to wxStrings in the locals? I need to add the watch AGAIN, even if the variable (now useless) remains in the locals.