https://bugs.winehq.org/show_bug.cgi?id=24387
--- Comment #35 from Andrea Vai andrea.vai@unipv.it --- Bug is still present in wine-1.7.51
I am sorry, but I am having some problems in attaching a new backtrace: following instructions at http://wiki.winehq.org/Backtraces I find this output from winedbg (*):
Wine-dbg>info process pid threads executable (all id:s are in hex) 0000000e 7 'services.exe' 00000022 3 _ 'winedevice.exe' 0000001b 3 _ 'plugplay.exe' 00000014 4 _ 'winedevice.exe'
and I don't know which pid to use for attaching the process, as none of them seems related to the program that, indeed, is currently running (msmoney.exe).
(*) I now realize that I am (perhaps (**)) using winedbg 1.7.18 (and I can't find a winedbg executable in the compiled 1.7.51 version, except in programs/winedbg/winedbg.exe.so, which gives me segmentation fault if I launch it). Don't know if this matters.
(**) I can't find a command line option of winedbg to get its version, so I can only guess that the version is 1.7.18 because this is the version number reported at the bottom of the page generated by typing "man winedbg". Don't know if this is a correct guess.