Hi!

Sorry if this has come up already, I've searched the NG but didn't find anything. I'm new to Ddbg, so I've probably made something wrong, but ... anyway, let's see.

Here's what happens:

Ddbg 0.10 beta - D Debugger
Copyright (c) 2007 Jascha Wetzel
see http://ddbg.mainia.de/doc.html for documentation

Loading symbols from wb.exe
->r
ntdll.dll loaded at 0x7c910000
KERNEL32.dll loaded at 0x7c800000
USER32.dll loaded at 0x7e360000
GDI32.dll loaded at 0x77ef0000
4invalid UTF-8 sequence
->

That UTF-8 thing seems to mess up Ddbg somehow, it just doesn't work. Is there anything I can do about it?

-Mike

Mike wrote:
> Loading symbols from wb.exe
> ->r
> ntdll.dll loaded at 0x7c910000
> KERNEL32.dll loaded at 0x7c800000
> USER32.dll loaded at 0x7e360000
> GDI32.dll loaded at 0x77ef0000
> 4invalid UTF-8 sequence
> ->
> 
> That UTF-8 thing seems to mess up Ddbg somehow, it just doesn't work. Is there anything I can do about it?

there has been an issue where some dll names caused that to happen. for the case given at that time, it was fixed, though.
i'd like to reproduce this problem to see what's going on. could you send me whatever i need to do so?
besides that, you can try to issue another 'r' after that message.

Mike wrote:
> Hi!
> 
> Sorry if this has come up already, I've searched the NG but didn't find anything. I'm new to Ddbg, so I've probably made something wrong, but ... anyway, let's see.
> 
> Here's what happens:
> 
> Ddbg 0.10 beta - D Debugger
> Copyright (c) 2007 Jascha Wetzel
> see http://ddbg.mainia.de/doc.html for documentation
> 
> Loading symbols from wb.exe
> ->r
> ntdll.dll loaded at 0x7c910000
> KERNEL32.dll loaded at 0x7c800000
> USER32.dll loaded at 0x7e360000
> GDI32.dll loaded at 0x77ef0000
> 4invalid UTF-8 sequence
> ->
> 
> That UTF-8 thing seems to mess up Ddbg somehow, it just doesn't work. Is there anything I can do about it?
> 
> -Mike

I've seen the UTF problem with fixed length strings (writefln has the same problem). Initializing them to 0 before using fixes the problem .

Are you sure that writefln or writef (or format / sformat) aren't throwing an exception rather than ddbg ?


Set a break point to the 1st line of code (main or winmain) and then r. Step thru the program to see where it dies.

dickl Wrote:

> I've seen the UTF problem with fixed length strings (writefln has the same problem). Initializing them to 0 before using fixes the problem .

I don't use any fixed-length strings. It's either literals or "string" (D 2.0). It occured to me: Maybe it's D 2.0 causing this problem?

> Are you sure that writefln or writef (or format / sformat) aren't throwing an exception rather than ddbg ?

No, without Ddbg it's just an Access Violation. I found the null reference and fixed it in the meantime, writefln worked without problem all the time (I use %s with all strings). Ddbg still gives me the error, even if the code now runs without bugs.

> Set a break point to the 1st line of code (main or winmain) and then r. Step thru the program to see where it dies.

Tried that already, doesn't work.

-Mike

Jascha Wetzel <[firstname]@mainia.de> Wrote:

> there has been an issue where some dll names caused that to happen. for
> the case given at that time, it was fixed, though.
> i'd like to reproduce this problem to see what's going on. could you
> send me whatever i need to do so?
> besides that, you can try to issue another 'r' after that message.

A second 'r' does nothing.
I'll send you a zipfile shortly. Thanks!

-Mike