Fabian suggested that I will, next time, use the bt command in the debugger which I did and the backtrack is listed below.
Can you make any sense out of it?
One more question.
In order to enable the debugger I had to setup some registry entries. I did not do it manually, instead I had wine installed from source using ./tools/wineinstall
Is there a similar procedure to setup everything when you install from rpm file? are the tools such as winecheck available when installing from rpm?
David Harel wrote:
Thanks for your patience, bt track below.
Fabian Cenedese wrote:
Wine-dbg>bt
Next time say yes and enter bt for backtrace. Like that you can see
what functions where called. Post this output.
Backtrace:
=>0 0x40914812 (DBSRV32.DLL.FormatDouble+0xa in DBSRV32.DLL) (ebp=4050dcbd)
1 0x0000004e (__libc_res+0x26 [interp.c]) (ebp=13000000)
*** Invalid address 0x13000000 (dbd32.exe..rsrc+0x12bd9000)
I do see the splash screen of the dbd32.exe application.
bye Fabi
-- Thanks.
David Harel,
==================================
Home office +972 4 6921986 Fax: +972 4 6921986 Cellular: +972 54 534502 Snail Mail: Amuka D.N Merom Hagalil 13802 Israel Email: hareldvd@xxxxxxxxxxxxxxxx
_______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users