RE: Help with GetConsoleWindow()

[Ewert, Mark]

I think you're right. The program seems to crash at a point much later
than the GetConsoleWindow call. Here's what I see:

"wine: Unhandled exception (thread 000d), starting debugger...
WineDbg starting on pid 0x8
Unhandled exception: page fault on write access to 0x41a417a4 in 32-bit
code (0x10007239).
In 32 bit mode."

A window pops up that says:

"Uhandled page fault on write access to 0x41a417a4 at address 0x10007239
Do you wish to debug it?"

When I click yes I get a dump of all the register/memory locations. Is
there anything in particular I should look for?

-----Original Message-----
From: Eric Pouech [mailto:[e-mail]] 
Sent: Saturday, September 18, 2004 12:12 AM
To: Ewert, Mark
Cc: [e-mail]
Subject: Re: Help with GetConsoleWindow()
> Any ideas on what GetConsoleWindow() should actually return?

it should return the handle of the window (user32) where the console 
actually runs (it is attached to a console).
Anyway, are you sure the segfault you see is related to returning a non 
NULL value in GetConsoleWindow compared to another bug in Wine (because 
you are running on another codepath - the first one being the graphical 
display).
Where does you program actually crash ?
A+

Help with GetConsoleWindow()

[Saulius Krasuckas]

On Mon, 20 Sep 2004, Ewert, Mark wrote:
> "wine: Unhandled exception (thread 000d), starting debugger...
> WineDbg starting on pid 0x8
> Unhandled exception: page fault on write access to 0x41a417a4 in 32-bit
> code (0x10007239).
> In 32 bit mode."
>
> A window pops up that says:
>
> "Uhandled page fault on write access to 0x41a417a4 at address 0x10007239
> Do you wish to debug it?"

Is this oming from another thread or even another process?  IMHO, you
should try running in some way similar to this:

$ WINEDEBUG=+loaddll,+process,+tid wine ...

to see more interesting info in the output of Wine.
> When I click yes I get a dump of all the register/memory locations. Is
> there anything in particular I should look for?

IMO, no.  Are you receiving an interactive prompt of "Wine-dbg>" in your
console?  If yes, better try typing command "bt" to get the backtrace,
then.  Maybe the "bt all" command would help more.

My $.01, my $.01.