Is this a known problem? When I try to run the callwave install program, or the callwave program itself, I merely get:
fixme:win32:PE_CreateModule Security directory ignored err:seh:start_debugger Couldn't start debugger (debugger/winedbg 134640112 24) (2) Read the Wine Developers Guide on how to set up winedbg or another debugger
Is this a configuration error on my part? Either way, is there some information I need to give to get this fixed? I appreciate it.
Thanks
Steven Walter wrote:
Is this a known problem? When I try to run the callwave install program, or the callwave program itself, I merely get:
fixme:win32:PE_CreateModule Security directory ignored err:seh:start_debugger Couldn't start debugger (debugger/winedbg 134640112 24) (2) Read the Wine Developers Guide on how to set up winedbg or another debugger
the first fixme is harmless the second part means that an exception occured in the program (likely a seg fault) and the debugger couldn't be launched to display the context of the error read the doc and properly set up the debugger for this information, and/or look at the various ways to submit a full bug report (running with -debugmsg +relay and quoting the 500 lines before the point the exception is triggered is quite always a good starting point)
A+
On Sat, Sep 22, 2001 at 09:26:22AM +0200, eric pouech wrote:
the first fixme is harmless the second part means that an exception occured in the program (likely a seg fault) and the debugger couldn't be launched to display the context of the error read the doc and properly set up the debugger for this information, and/or look at the various ways to submit a full bug report (running with -debugmsg +relay and quoting the 500 lines before the point the exception is triggered is quite always a good starting point)
Attached is the /entire/ relay log. Its pretty obvious that it doesn't get far. Additionally, the debugger seems to get killed for some reason; it pops up, stays for a fraction of a second, and is then killed. I get the message "Terminated" in the shell where I was running wine.
Steven Walter wrote:
On Sat, Sep 22, 2001 at 09:26:22AM +0200, eric pouech wrote:
the first fixme is harmless the second part means that an exception occured in the program (likely a seg fault) and the debugger couldn't be launched to display the context of the error read the doc and properly set up the debugger for this information, and/or look at the various ways to submit a full bug report (running with -debugmsg +relay and quoting the 500 lines before the point the exception is triggered is quite always a good starting point)
Attached is the /entire/ relay log. Its pretty obvious that it doesn't get far. Additionally, the debugger seems to get killed for some reason; it pops up, stays for a fraction of a second, and is then killed. I get the message "Terminated" in the shell where I was running wine.
what's strange is that the relay posted only targets the debugger process, not the process creating the exception... (the one creating the exception is 080671f0 and never shows up in the trace) how did you run your program ? which wine version are you using ? (from your previous post, the debugger now starts)
A+
On Sat, Sep 22, 2001 at 09:55:10PM +0200, eric pouech wrote:
what's strange is that the relay posted only targets the debugger process, not the process creating the exception... (the one creating the exception is 080671f0 and never shows up in the trace) how did you run your program ? which wine version are you using ? (from your previous post, the debugger now starts)
Yes, the debugger starts, but I don't really think its configured correctly, still. In order to get it to start, I have to start wine from the directory I built it, so that it will find ./debugger/winedbg. Shouldn't it look in the path for "winedbg," rather than only the current directory?
Anyway, I started the program, from the directory where I built wine, as "wine -debugmsg +relay 'c:\iamsetup.exe'" Wine version is CVS from yesterday, though it has occurred in the CVS version for several weeks; I've never not had the problem.
Possibly an interesting note, when I run as "wine -debugmsg +relay", and the debugger is unable to start for whatever reason, no messages are printed that aren't also printed with just "wine". "wine -debugmsg +all" does, however, log extra stuff. Attached is the latter part of what that yields.
Yes, the debugger starts, but I don't really think its configured correctly, still. In order to get it to start, I have to start wine from the directory I built it, so that it will find ./debugger/winedbg. Shouldn't it look in the path for "winedbg," rather than only the current directory?
well, if you want to run wine from the directory it's built in, you need to : 1/ add to LD_LIBRARY_PATH the dlls subdir 2/ add to PATH the wine's dir check out the tools/winelauncher for some more on this
Possibly an interesting note, when I run as "wine -debugmsg +relay", and the debugger is unable to start for whatever reason, no messages are printed that aren't also printed with just "wine". "wine -debugmsg +all" does, however, log extra stuff. Attached is the latter part of what that yields.
first, it's not a good idea to jam wine-devel with lots of logs. best practice is to put the log (if rather large, > 10k for example) somewhere on the web and put only the URL for retrieving the log in your mail (this will save bandwidth)
08068490:trace:win32:dump_exports *******EXPORT DATA******* 08068490:trace:win32:dump_exports 08068490:trace:seh:EXC_RtlRaiseException code=c0000005 flags=0 08068490: queue_exception_event( first=1, record={context={flags=00000000,eax=402a2a00,ebx=4033fe38,ecx=ffffffff,edx=40856c8b,esi=0000000f,edi=967c77e5,ebp=40856c8c,eip=402a2ab2,esp=40856694,eflags=00210246,cs=0023,ds=002b,es=002b,fs=008f,gs=0000,dr0=00000000,dr1=00000000,dr2=00000000,dr3=00000000,dr6=00000000,dr7=00000000,float={00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000}},rec={code=c0000005,flags=0,rec=(nil),addr=0x402a2ab2,params={0,967c77e5}} )
the dumping of export badly crashes did you test that your program isn't infected by a virus ? if not, what gives dumping (with winedump) the file (tools/winedump dump iamsetup.exe -x)
A+