I have a struct like this:

struct A {
    // some members
    A[] subAs;
}

When debugging this, I can see the number of members in subAs, but if I try
to inspect them using the IDE, I get:
->Parser: Invalid expression!

This applies to all array members (except basic array types)

Is there a bug in the gdb interface? The command line works, but I like just clicking on the variables :)

I'm using descent/ddbg 0.10Beta/Dmd 1.022, but I've also had the same problem with C::B and earlier versions of both ddbg and dmd.

You'd need to know if it's a problem of Descent / Code::Blocks or ddbg. If you pass the expression to ddbg in the command line, do you get the same error? How does the expression look like?

Simen Haugen wrote:
> I have a struct like this:
> 
> struct A {
>     // some members
>     A[] subAs;
> }
> 
> When debugging this, I can see the number of members in subAs, but if I try to inspect them using the IDE, I get:
> ->Parser: Invalid expression!
> 
> This applies to all array members (except basic array types)
> 
> Is there a bug in the gdb interface? The command line works, but I like just clicking on the variables :)
> 
> I'm using descent/ddbg 0.10Beta/Dmd 1.022, but I've also had the same problem with C::B and earlier versions of both ddbg and dmd.
> 
> 

"Ary Manzana" <ary@esperanto.org.ar> wrote in message news:feft5u$62m$1@digitalmars.com...
> You'd need to know if it's a problem of Descent / Code::Blocks or ddbg. If you pass the expression to ddbg in the command line, do you get the same error? How does the expression look like?

How can i see the debugger command descent sends ddbg? It doesn't show in the console.

Everything works in the command line, thats why I tought it might have something to do with the gdb interface (as I had the same problem with C::B)

Simen Haugen wrote:
> "Ary Manzana" <ary@esperanto.org.ar> wrote in message news:feft5u$62m$1@digitalmars.com...
>> You'd need to know if it's a problem of Descent / Code::Blocks or ddbg. If you pass the expression to ddbg in the command line, do you get the same error? How does the expression look like?
> 
> How can i see the debugger command descent sends ddbg? It doesn't show in the console.
> 
> Everything works in the command line, thats why I tought it might have something to do with the gdb interface (as I had the same problem with C::B) 

since descent uses the ddbg interface directly, it should work anyway. therefore, these have to be separate problems that create the same symptom.
C::B has a few issues with the interfacing. you can check the gdb interface on the command line, too, by invoking the batch file directly.