Some strange winedbg regression...

[Lionel Ulmer]

On Sat, Dec 21, 2002 at 05:49:23PM +0100, Eric Pouech wrote:
> > So I was wondering how to debug this ? I tried to attach 'gdb' to it (and it
> > works) but how do I know which symbols to load (winedbg being a script, wine
> > having no code except linking to DLLs, ....) ?
> load miscemu/wine in gdb, it'll get what you're looking for

OK, what happens is that the application is loading the DINPUT library...
And at DLL load time, it adds a low-level hook for the keyboard (I wonder
why only for the keyboard and not the mouse, but well, that's another
problem :-) ).

And it seems that the invocation of this hook from the wineconsole makes
Wine crash. I think that the problem is that the DLL is loaded from the
application's context and called from the console context.

Now, one could do the same for the mouse, ie install the hook only later on
when acquiring the keyboard, but well, I think the problem would be the same
if the debugger is started after the 'acquire'.

So I wonder how to 'fix' this... I think I know Eric's answer : use GDB's
proxy stuff and debug Wine using a non-Wine application :-)

                     Lionel

-- 
		 Lionel Ulmer - http://www.bbrox.org/