[Wine] New Winecfg crash
Evil
wine at eternaldusk.com
Sat Dec 10 10:42:29 CST 2005
Robert Reif wrote:
> Does this patch fix the problem?
Unfortunately, the patch didn't seem to clear up my crash:
[evil at vampyre wine] $ WINEDEBUG=+wave winecfg
trace:wave:ALSA_widMessage (0, DRVM_INIT, 00000000, 00000000, 00000000);
trace:wave:ALSA_widMessage (0, WIDM_GETNUMDEVS, 00000000, 00000000,
00000000);
trace:wave:ALSA_wodMessage (0, DRVM_INIT, 00000000, 00000000, 00000000);
trace:wave:ALSA_wodMessage (0, WODM_GETNUMDEVS, 00000000, 00000000,
00000000);
trace:wave:ALSA_wodMessage (0, WODM_GETNUMDEVS, 00000000, 00000000,
00000000);
trace:wave:ALSA_widMessage (0, WIDM_GETNUMDEVS, 00000000, 00000000,
00000000);
trace:wave:ALSA_wodMessage (0, WODM_GETDEVCAPS, 00000000, 7FBFEE34,
00000054);
trace:wave:wodGetDevCaps (0, 0x7fbfee34, 84);
trace:wave:ALSA_widMessage (0, WIDM_GETDEVCAPS, 00000000, 7FBFEE34,
00000050);
trace:wave:widGetDevCaps (0, 0x7fbfee34, 80);
trace:wave:ARTS_DriverProc (00000000, 0x7fdfbc70, 00000001, 00000000,
00000000)
trace:wave:ARTS_drvLoad ()
trace:wave:ARTS_WaveInit called
*** glibc detected *** free(): invalid pointer: 0x7c0a6cd0 ***
wine: Assertion failed at address 0xffffe410 (thread 0009), starting
debugger...
-Jesse
More information about the wine-users
mailing list