the nightly build C::B doesn't work with ddbg i don't get why?
i 've set the compiler and linker option all get -g
and also set the ddbg name to ddbg_gdb.exe and set it as the debugger
if i set a breakpoint in C::B , and start debugging i see the following:

Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting breakpoints
Debugger finished with status 1

any idea of what happened?
and ain't new type STL stuffs all C++ things?

Davidl@126.com wrote:
> 
> the nightly build C::B doesn't work with ddbg i don't get why?
> i 've set the compiler and linker option all get -g
> and also set the ddbg name to ddbg_gdb.exe and set it as the debugger
> if i set a breakpoint in C::B , and start debugging i see the following:
> 
> Registered new type: wxString
> Registered new type: STL String
> Registered new type: STL Vector
> Setting breakpoints
> Debugger finished with status 1
> 
> any idea of what happened?
> and ain't new type STL stuffs all C++ things?

I've just download the latest 3/14/07 and it work fine with me.

vtp

oh, i know it's the C::B's bug, it couldn't send the executable binary which
is in a path contain spaces to ddbg correctly.
now i'm playing around with ddbg happily!!

err, another codeblock bug is create two workspace, and open the source of them
in the main window, and then close the first opened workspace , and then click the
source file which is opened there. C::B would hang.

err, another inconvenience of C::B is no code completion.

and also is there any possible to view the different call stack frame args ?
like in a func which get called from main(char[][] args), can i watch the main
args by cast(char[][])args ? now it's impossible of doing so , it gives me
symbol cast(char[][])args not found, and switch call stack frame is used for what?
right click to see it in the call stack window.

Though the problems i stated here mostly are C::B related, please someone who is
familiar with C::B help me. Great thanks!!


>
> the nightly build C::B doesn't work with ddbg i don't get why?
> i 've set the compiler and linker option all get -g
> and also set the ddbg name to ddbg_gdb.exe and set it as the debugger
> if i set a breakpoint in C::B , and start debugging i see the following:
>
> Registered new type: wxString
> Registered new type: STL String
> Registered new type: STL Vector
> Setting breakpoints
> Debugger finished with status 1
>
> any idea of what happened?
> and ain't new type STL stuffs all C++ things?

<Davidl@126.com> wrote in message news:<op.to76dfvs8pkrw6@aics-server2>...
> err, another inconvenience of C::B is no code completion.
I'm using the latest nightly build and code completion works nice.

> and also is there any possible to view the different call stack frame args
Debug->Debugging windows->Call stack

> like in a func which get called from main(char[][] args), can i watch the
> main
> args by cast(char[][])args ? now it's impossible of doing so , it gives me
> symbol cast(char[][])args not found, and switch call stack frame is used
> for what?
> right click to see it in the call stack window.
I don't understand what you mean.
Are you saying that in this code:
Import std.stdio;

void main(char[][] args)
{
    writefln(cast(char[][])args);
}
You get an unknown symbol error?
Ddbg doesn't support arrays yet, so it wont show in the watches window if that’s what you mean.

在 Sat, 17 Mar 2007 06:31:33 +0800，Simen <simen.haugen@pandavre.com> 写道:

> <Davidl@126.com> wrote in message news:<op.to76dfvs8pkrw6@aics-server2>...
>> err, another inconvenience of C::B is no code completion.
> I'm using the latest nightly build and code completion works nice.
>
>> and also is there any possible to view the different call stack frame args
> Debug->Debugging windows->Call stack

i mean in the call stack , u see severl different frames of different funcs
, i want to see those args of those funcs
>
>> like in a func which get called from main(char[][] args), can i watch the
>> main
>> args by cast(char[][])args ? now it's impossible of doing so , it gives me
>> symbol cast(char[][])args not found, and switch call stack frame is used
>> for what?
>> right click to see it in the call stack window.
> I don't understand what you mean.
> Are you saying that in this code:
> Import std.stdio;
>
> void main(char[][] args)
> {
>     writefln(cast(char[][])args);
> }
> You get an unknown symbol error?
> Ddbg doesn't support arrays yet, so it wont show in the watches window if that’s what you mean.

nope, i mean
when code get run into line 3, i want to use cast(char[][])main.args to
see those args passed to main

1 void hello(char[] name)
2 {
3   writefln(name);
4 }
5 void main(char[][]args)
6 {
7   hello(arg[1]);
8 }

Davidl wrote:
> nope, i mean
> when code get run into line 3, i want to use cast(char[][])main.args to
> see those args passed to main
> 
> 1 void hello(char[] name)
> 2 {
> 3   writefln(name);
> 4 }
> 5 void main(char[][]args)
> 6 {
> 7   hello(arg[1]);
> 8 }

you cannot evaluate expressions in other stackframes than the current, yet. i will add this in one of the next releases.