Sadly no, I don't get the crash dialogue. A virtual Desktop opens and closes a second later. I tried the manual for the backtrace from
here.
It gives me the following output:
1.Terminal:
Code: Select all
Quake II Complete$ wine quake2.exe
err:seh:setup_exception_record stack overflow 880 bytes in thread 003c eip 7bc4050f esp 00230fc0 stack 0x230000-0x231000-0x330000
Quake II Complete$
2. Terminal:
Code: Select all
Wine-dbg>info process
pid threads executable (all id:s are in hex)
0000000e 6 'services.exe'
00000021 3 \_ 'winedevice.exe'
0000001a 3 \_ 'plugplay.exe'
00000012 4 \_ 'winedevice.exe'
00000008 1 'winedbg.exe'
Wine-dbg>attach 0x0029
Can't attach process 0029: error 5
Wine-dbg>fixme:console:CONSOLE_DefaultHandler Terminating process 2f on event 0
Wine-dbg>set $BreakOnFirstChance=0
No process loaded, cannot execute 'set $BreakOnFirstChance=0'
-> This doesn't work, or?
When I try this:
If for some reason, you cannot attach to your running process, invoke your program like so:
Code: Select all
Quake II Complete$ wine winedbg quake2.exe
WineDbg starting on pid 002a
0x7b85f647: movl %edi,0x4(%esp)
Wine-dbg>set $BreakOnFirstChance=0
Wine-dbg>cont
err:seh:setup_exception_record stack overflow 880 bytes in thread 002b eip 7bc4050f esp 00240fc0 stack 0x240000-0x241000-0x340000
Process of pid=002a has terminated
Process of pid=002d has terminated
This doesn'tlook like the backtrace in the example

Is it helping in anyway? Am I doing something wrong with the backtrace?
THX for the help!!