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

Jussi Jumppanen Wrote:

> I get this error:
> 
>   Error: Win32 Exception

You can ignore this bug report.

I checked this again with the latest Ddbg v0.0.4.5 alpha version and it works as expected :)

> For example if I run this command
>   ->= test
> 
> I get this output:
>   0x00890fa000000003
> 
> But if I run this command:
>   ->=test

I still think this would be a "nice to have" change ;)

Cheers Jussi Jumppanen
Author: Zeus for Windows IDE
http://www.zeusedit.com