Lester L. Martin II Wrote:

> Charlie Wrote:
> 
> > > Walter, I'd like to do more with GDB, and expand the patch, but since the
> > DWARF2
> > > line number info is broke, I can't use GDB to do anything but stack traces
> > on
> > > segfaults.  I would appreciate if you would put a higher priority on this
> > item.
> > > Although there are still "show stopper" bugs, most of them aren't bugs
> > people
> > > run into on a daily basis.  Debugging is something that most people do on
> > a
> > > daily basis, so I would argue it should be of high importance.
> > 
> > We Win32 users would certainly like more debug info also :).  I wonder why this wasn't the first thing to be developed, seems it would be enourmously helpful from the start.
> > 
> > Charlie
> > 
> > 
> > "John Demme" <me@teqdruid.com> wrote in message news:d3sq2d$1094$1@digitaldaemon.com...
> > > I've finally gotten my GDB patch working.  It's able to demangle most D
> > symbols,
> > > but a few weird ones still show up.  Anyway, the announcement (along with
> > > directions) are here:
> > > http://dsource.org/forums/viewtopic.php?t=734
> > >
> > > Please report bugs on the dsource forum, instead of cluttering up this NG.
> > >
> > > Walter, I'd like to do more with GDB, and expand the patch, but since the
> > DWARF2
> > > line number info is broke, I can't use GDB to do anything but stack traces
> > on
> > > segfaults.  I would appreciate if you would put a higher priority on this
> > item.
> > > Although there are still "show stopper" bugs, most of them aren't bugs
> > people
> > > run into on a daily basis.  Debugging is something that most people do on
> > a
> > > daily basis, so I would argue it should be of high importance.
> > >
> > > John Demme
> > >
> > >
> > 
> > 
> 



 how do you get ddbg running for poseidon.  it gives me this error on ddbg 4invalid UTF-8 sequence.
 Is it poseidon or ddbg because it happens in loading the windows dlls. Is there a way to fix it.
'd rather use it with Poseidon than codeblocks becaus of codecompletion and it's like Eclipse but less size so I don't get all those extra programming languages I won't use.

 Well thanks for your help,
 Lester L. Martin II

Lester L. Martin II wrote:
>  how do you get ddbg running for poseidon.  it gives me this error on ddbg 4invalid UTF-8 sequence.
>  Is it poseidon or ddbg because it happens in loading the windows dlls. Is there a way to fix it.

there is a known problem with ddbg on windows vista that causes these utf-8 errors. the fix will be in the next release.
if you don't use vista, please post everything i need to reproduce the problem.
generally, try using ddbg from the command line to test whether an IDE causes a problem.

Jascha Wetzel wrote:
> Lester L. Martin II wrote:
>>  how do you get ddbg running for poseidon.  it gives me this error on ddbg 4invalid UTF-8 sequence.
>>  Is it poseidon or ddbg because it happens in loading the windows dlls. Is there a way to fix it.
> 
> there is a known problem with ddbg on windows vista that causes these utf-8 errors. the fix will be in the next release.
> if you don't use vista, please post everything i need to reproduce the problem.
> generally, try using ddbg from the command line to test whether an IDE causes a problem.

I get those on XP sometimes too.  But it only seems to happen when I run into some certain asserts or maybe exceptions.  I haven't been able to narrow it down, but I just wanted to say don't discount XP utf-8 problems because I've seen them too.   Ddbg 0.11 beta preview.

--bb

Bill Baxter Wrote:

> Jascha Wetzel wrote:
> > Lester L. Martin II wrote:
> >>  how do you get ddbg running for poseidon.  it gives me this error on
> >> ddbg 4invalid UTF-8 sequence.
> >>  Is it poseidon or ddbg because it happens in loading the windows
> >> dlls. Is there a way to fix it.
> > 
> > there is a known problem with ddbg on windows vista that causes these
> > utf-8 errors. the fix will be in the next release.
> > if you don't use vista, please post everything i need to reproduce the
> > problem.
> > generally, try using ddbg from the command line to test whether an IDE
> > causes a problem.
> 
> I get those on XP sometimes too.  But it only seems to happen when I run into some certain asserts or maybe exceptions.  I haven't been able to narrow it down, but I just wanted to say don't discount XP utf-8 problems because I've seen them too.   Ddbg 0.11 beta preview.
> 
> --bb


Ok It happens on XP and only when I use Poseidon to try and Debug this.  I'm using 0.11 preview.

Ok here's the code(rather simple actually;I was only going to use this to test the debugger): import tango.io.Console;

int main(char[][] args)
{
	char[] boo;
	Cout("Boo").flush;
	boo = Cin.get();
	Cout(boo).flush;
	Cin.get();
    return 0;
}

Now set up a project completely in Poseidon with this and press the little bug looking button.  Ok now it gives you the option to continue in a little debug screen.  Press the button that looks like play and you get:
Ddbg 0.11 beta preview2 - D Debugger
Copyright (c) 2007 Jascha Wetzel
see http://ddbg.mainia.de/doc.html for documentation

Loading symbols from C:\CB\Projects\asd\asd.exe
->nc
Starting debuggee in new console
->r
ntdll.dll loaded at 0x7c900000
KERNEL32.dll loaded at 0x7c800000
SHELL32.dll loaded at 0x7c9c0000
ADVAPI32.dll loaded at 0x77dd0000
RPCRT4.dll loaded at 0x77e70000
Secur32.dll loaded at 0x77fe0000
GDI32.dll loaded at 0x77f10000
USER32.dll loaded at 0x7e410000
msvcrt.dll loaded at 0x77c10000
SHLWAPI.dll loaded at 0x77f60000
Unknown breakpoint hit at ntdll.dll (0x7c901230) thread(1636)
IMM32.dll loaded at 0x76390000
unknown DLL loaded
COMCTL32.dll loaded at 0x773d0000
COMCTL32.dll loaded at 0x5d090000
4invalid UTF-8 sequence
->

with the last part being the error that I know is an error though it may have started at unknown dll loaded.

I have no windows vista so can't try to reproduce it there and I am using Poseidon svn trunk and DMD 1.023 with tango Thriller and a couple of other libraries not called upon to compile this executable and thereby non-important.

Any more information you want. I'll let you know as you ask for it. I can give you the whole enviroment(changed from default) to let you know how poseidon is set up but it'll probably happen under different enviroments.  All you have to do is set the DDBG location, The compilers; In project properties point all your  tango libs into it with the tango import pointed also.  Set -g option and -debug option(these are set defaultly for debugging so you can count that as irrelevant) and add -L+-g(dash ell plus dash jee) in other options as it doesn't give direct linker communication which means have the compiler pass the linker flags.

Ok that's all,
Lester L. Martin II

Ps: works fine in code blocks so I'm thinking it's something to do with how Poiseidon sent it the UTF string as it is compiled under phobos according to many.

Bill Baxter wrote:
> I get those on XP sometimes too.  But it only seems to happen when I run into some certain asserts or maybe exceptions.  I haven't been able to narrow it down, but I just wanted to say don't discount XP utf-8 problems because I've seen them too.   Ddbg 0.11 beta preview.

yes, for exceptions, especially those that carry messages from the debuggee, that may happen. i have such a testcase on the list for 0.11.

Lester L. Martin II wrote:
> Ok It happens on XP and only when I use Poseidon to try and Debug this.  I'm using 0.11 preview.
> ...

thanks, i'll look into it.

Jascha Wetzel Wrote:

> Lester L. Martin II wrote:
> > Ok It happens on XP and only when I use Poseidon to try and Debug this.  I'm using 0.11 preview. ...
> 
> thanks, i'll look into it.

ok, thankyou, but remember it may not be your problem.  It all works fine under code::blocks; its just Poseidon that's having problems using the debugger.

Lester L. Martin II Wrote:

> Jascha Wetzel Wrote:
> 
> > Lester L. Martin II wrote:
> > > Ok It happens on XP and only when I use Poseidon to try and Debug this.  I'm using 0.11 preview. ...
> > 
> > thanks, i'll look into it.
> 
> ok, thankyou, but remember it may not be your problem.  It all works fine under code::blocks; its just Poseidon that's having problems using the debugger.


Hey,

I just figured out it isn't a posiedon problem.  I tried ddbg seperately and found same error.  Well it does have something to do with the way Poseidon puts the program together vs the way Code::Blocks does it.  Try and compile the file with linking(eg no separate compilation and linking) and pass this flag to dmd : -L+-g; instead of linking with -g this should do the same(I'm not sure though and this may be my problem.).  If you know how Code::Blocks compiles the project and the way it differs from Poseidons way of building the project or lack of adding -g to the linker command then I think you'll be well on you way to figuring out the bug.  Thankyou for all your help and let me know if it is a -L+-g instead of link $ -g problem.  If you have any questions about the above then please let me know since I put this together quickly and it may sound non-coherent.

Lester L. Martin II