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+