Hello,
AVRStudio.exe hits an unimplemented msxml function and tries to start the debugger. For me this fails: /home/wine/wine/wine AvrStudio4/AVRStudio.exe fixme:ole:CoRegisterMessageFilter stub fixme:ole:CoRegisterMessageFilter stub fixme:ole:CoRegisterMessageFilter stub fixme:msxml:domdoc_createNode wine: Unhandled exception (thread 0009), starting debugger... err:winedbg:main Invalid event handle: 0x100
I run wine from the compilation directory, so I use the full path to wine. Aedebug has also the full path to winedbg.
In a log. I think these are the relevant lines:
0009:Call ntdll.NtCreateEvent(7babed44,001f0003,7babef0c,00000001,00000000) ret=7bb558ec 0009: create_event( access=001f0003, manual_reset=1, initial_state=0,inherit=1, name=L"" ) 0009: create_event() = 0 { handle=0x100 } 0009:Ret ntdll.NtCreateEvent() retval=00000000 ret=7bb558ec wine: Unhandled exception (thread 0009), starting debugger... ... 0009:trace:seh:start_debugger Starting debugger "/home/wine/wine/programs/winedbg/winedbg --auto 8 256" ... 0009:Call ntdll.NtWaitForMultipleObjects(00000001,7babebb8,00000000,00000000,00000000) ret=7bb914c5 0009: select( flags=4, cookie=0x7babe9d4, signal=(nil), timeout=0,handles={0x100} ) 0009: select() = PENDING 000c: *fd* (nil) -> 47 000d: *fd* 6 <- 47 000d: *fd* 8 <- 48 ... 000b: select() = PENDING 000d: event_op( handle=0x100, op=1 ) 000d: event_op() = INVALID_HANDLE err:winedbg:main Invalid event handle: 0x100 000d: terminate_process( handle=0xffffffff, exit_code=0 ) 000d: terminate_process() = 0 { self=1 } 000d: *killed* exit_code=0 000b: *killed* exit_code=0 000a: *killed* exit_code=0 0009: *killed* exit_code=0
Any help on what is going wrong?
Bye
Uwe Bonnes wrote:
Hello,
AVRStudio.exe hits an unimplemented msxml function and tries to start the debugger. For me this fails: /home/wine/wine/wine AvrStudio4/AVRStudio.exe fixme:ole:CoRegisterMessageFilter stub fixme:ole:CoRegisterMessageFilter stub fixme:ole:CoRegisterMessageFilter stub fixme:msxml:domdoc_createNode wine: Unhandled exception (thread 0009), starting debugger... err:winedbg:main Invalid event handle: 0x100
I run wine from the compilation directory, so I use the full path to wine. Aedebug has also the full path to winedbg.
I suppose it's a vanilla Wine tree... what happens is that the event used to synchronize with the debugger is not valid in the debugger what happens is that the event doesn't exist (or no longer exist) when the debugger starts. this can happen if either the crashing program died at some point... where does in your log process 8 terminate ? A+
"Eric" == Eric Pouech eric.pouech@wanadoo.fr writes:
Eric> Uwe Bonnes wrote: >> Hello, >> >> AVRStudio.exe hits an unimplemented msxml function and tries to start >> the debugger. For me this fails: /home/wine/wine/wine >> AvrStudio4/AVRStudio.exe fixme:ole:CoRegisterMessageFilter stub >> fixme:ole:CoRegisterMessageFilter stub >> fixme:ole:CoRegisterMessageFilter stub fixme:msxml:domdoc_createNode >> wine: Unhandled exception (thread 0009), starting debugger... >> err:winedbg:main Invalid event handle: 0x100 >> >> I run wine from the compilation directory, so I use the full path to >> wine. Aedebug has also the full path to winedbg. Eric> I suppose it's a vanilla Wine tree... what happens is that the Eric> event used to synchronize with the debugger is not valid in the Eric> debugger what happens is that the event doesn't exist (or no Eric> longer exist) when the debugger starts. this can happen if either Eric> the crashing program died at some point... where does in your log Eric> process 8 terminate ? A+
Eric,
I don't see any abort for a process "8":
Actually the last lines of a +all log are: 000d: debug_process( pid=0008, attach=1 ) 000b: *attached* 000b: *signal* signal=10 000b: *signal* signal=19 000a: *attached* 000a: *signal* signal=19 0009: *attached* 0009: *signal* signal=19 000b: *signal* signal=19 000b: *signal* signal=19 000d: debug_process() = 0 0009: select( flags=8, cookie=0x7bd99c04, signal=(nil), timeout=1128291881.459378 (-0.000466), handles={} ) 0009: select() = PENDING 000a: select( flags=8, cookie=0x7a6ddc04, signal=(nil), timeout=1128291881.459324 (-0.000705), handles={} ) 000a: select() = PENDING 000b: select( flags=8, cookie=0x7a3fdc04, signal=(nil), timeout=1128291881.459438 (-0.000801), handles={} ) 000b: select() = PENDING 000d: event_op( handle=0x100, op=1 ) 000d: event_op() = INVALID_HANDLE err:winedbg:main Invalid event handle: 0x100 000d: terminate_process( handle=0xffffffff, exit_code=0 ) 000d: terminate_process() = 0 { self=1 } 000d: *killed* exit_code=0 000b: *killed* exit_code=0 000a: *killed* exit_code=0 0009: *killed* exit_code=0 wineserver: exiting (pid=9714)
Eric,
I don't see any abort for a process "8":
Yeah, that's not the issue: the debuggee is made of threads 9,a,b (and the debugger as a pid c and its main thread is d), and is still running when the event is set by the debugger.
Dumb question: are you running on a vanilla wine tree (ie not modified)? A+
"Eric" == Eric Pouech eric.pouech@wanadoo.fr writes:
>> Eric, >> >> I don't see any abort for a process "8": Eric> Yeah, that's not the issue: the debuggee is made of threads 9,a,b Eric> (and the debugger as a pid c and its main thread is d), and is Eric> still running when the event is set by the debugger.
Eric> Dumb question: are you running on a vanilla wine tree (ie not Eric> modified)? A+
I (repeatedly) purged all changes, and "cvs update -PAd" no longer returns and "M " or "C " entries. However I run wine not installed, e.g. I start wine with the fully qualified path and also the Aedebug registry entry contains the full path.
What about trying yourself? You can download switchercad from http://ltspice.linear.com/software/swcadiii.exe without any registration, It's about 6 MByte download, and it installs without problems. The programm author, Mike Engelhardt, has always been helpfull questions.
Bye
Uwe Bonnes bon@elektron.ikp.physik.tu-darmstadt.de writes:
I (repeatedly) purged all changes, and "cvs update -PAd" no longer returns and "M " or "C " entries. However I run wine not installed, e.g. I start wine with the fully qualified path and also the Aedebug registry entry contains the full path.
That's most likely the problem, if you specify the path to the winedbg wrapper script it gets launched as a Unix process, and doesn't inherit handles. Simply use 'winedbg' in the AeDebug entry, it should work fine when running from the source tree too.
"Alexandre" == Alexandre Julliard julliard@winehq.org writes:
Alexandre> Uwe Bonnes bon@elektron.ikp.physik.tu-darmstadt.de writes: >> I (repeatedly) purged all changes, and "cvs update -PAd" no longer >> returns and "M " or "C " entries. However I run wine not installed, >> e.g. I start wine with the fully qualified path and also the Aedebug >> registry entry contains the full path.
Alexandre> That's most likely the problem, if you specify the path to Alexandre> the winedbg wrapper script it gets launched as a Unix Alexandre> process, and doesn't inherit handles. Simply use 'winedbg' in Alexandre> the AeDebug entry, it should work fine when running from the Alexandre> source tree too.
Thanks, that's the problem.
Will wine now start the installed winedbg in the path or the winedbg from the path where wine was started from?
Uwe Bonnes bon@elektron.ikp.physik.tu-darmstadt.de writes:
Will wine now start the installed winedbg in the path or the winedbg from the path where wine was started from?
The first one it finds in WINEDLLPATH, which should be in the source tree if you are using the standard wine wrapper script.
-
Alexandre Julliard -
Eric Pouech -
Uwe Bonnes