Possible Ddbg-0.0.3 Bug?
Jussi Jumppanen
jussij at zeusedit.com
Wed Mar 14 17:49:09 PDT 2007
While testing the Zeus editor with the Ddbg-0.0.3 release I came
across what appears to be a minor bug but I might be wrong ;)
Given this bit of code:
uint printArgs(char[][] _D4argsAAa)
{
uint numchars;
char[] _D4testAa = "asdfqwer1234";
float[] _D4ztuiAf;
_D4ztuiAf ~= [234.6578];
}
when I set a break point on this line:
char[] _D4testAa = "asdfqwer1234";
and run the debugger up to this breakpoint I get this
debugger output:
Breakpoint 0 hit
debuggee1.d:43 0x40201d
char[] _D4testAa = "asdfqwer1234";
If I then run this command:
->= _D4testAa
I get this error:
Error: Win32 Exception
Yet if I run this this command:
->= some_random_text
I get a nice user friendly warning message:
Symbol some_random_text not found
If possible I think rather than throwing an exception and dying,
the debugger should generate a similar user friendly message.
One other suggestion would be could the debugger be changed to
better parse the '=' command?
For example if I run this command
->= test
I get this output:
0x00890fa000000003
But if I run this command:
->=test
I get this output:
Unknown command '=test' ignored!
Cheers Jussi Jumppanen
Author: Zeus for Windows IDE
http://www.zeusedit.com
More information about the Digitalmars-d-debugger
mailing list