User forums > Nightly builds
The 18 april 2006 build is out.
skirby:
Hello,
Here is a simple example which show you a bug with the debugger (with that build and probably previous one)
You can find the project here:
http://www.badongo.com/file/498569
Debug the program.
You should have a screen like that
Now if you trace the following instruction: strcpy(sStr, "azéerty");
All buttons of the debugger toolbar become disabled.
I really hope you could fix that problem.
Thanks and have a nice day
Szabadember:
The same bug here!!!
If you watch strings with non-english characters (áéűőúüöó for example), all buttons in the debug menu become disabled.
I've encountered another bug: if you clear all breakpoints with the command 'Clear all breakpoints' in the debug menu, the red circles do not disappear.
MoonKid:
--- Quote from: killerbot on April 18, 2006, 08:46:50 pm ---ansi build
--- End quote ---
The editorsettings-crash-bug is still alive in this version.
MortenMacFly:
--- Quote from: Szabadember on April 19, 2006, 05:32:15 pm ---The same bug here!!!
If you watch strings with non-english characters (áéűőúüöó for example), [...]
--- End quote ---
I tried to debug that bastard. That's unfortunately some "deep-level stuff". When the event DebuggerGDB::OnGDBOutput is fired from the piped process the event.GetString() already holds the wrong string. So it must be related to the way how stdout and stcerr are obtained / converted in PipedProcess. I'm currently inspecting cbTextInputStream::ReadLine() and cbTextInputStream::NextChar() which could be the cause. I'm reporting this for those who may have more knowledge than I...
With regards, Morten.
Edit: That's really strange... if I inspect the memory of the string using C::B it clearly shows the "right stuff", passing a "display mystring.c_str()" to gdb seems to work, too. Hence it could be the way how STL strings are parsed in the debugger script (gdb_types.script)...?! Anybody else working on that can help?!
Navigation
[0] Message Index
[*] Previous page
Go to full version