Hi, OK - maybe I'm getting close. I have a consistent failure across 4 different VSTs. I'm looking at a number of different VSTs running under jack_fst and then seeing what happens with the crash using WINEDEBUG=+something. Since the file wine/dlls/ntdll/virtual.c was changed in the set of changes that caused the crash for me, and since there is a debug channel called ntdll, I decided to give it a try. Interesting results. Here are 4 different VST. They all fail the same way, and they are all doing more or less the same thing inside of ntdll when they fail: flash mark $ WINEDEBUG=+ntdll jack_fst vst_dir/Ambience.dll <SNIP> trace:ntdll:NtCreateFile handle=0x7f754580 access=80000000 name=L"\\??\\C:\\windows\\win.ini" objattr=00000040 root=(nil) sec=(nil) io=0x7f754584 alloc_size=(nil) attr=00000080 sharing=00000001 disp=1 options=00000050 ea=(nil).0x00000000 trace:ntdll:NtQueryInformationFile (0x60,0x7f75457c,0x7f754584,0x00000024,0x00000004) trace:ntdll:FILE_GetNtStatus errno = 13 trace:ntdll:FILE_GetNtStatus errno = 13 trace:ntdll:FILE_GetNtStatus errno = 13 Segmentation fault flash mark $ flash mark $ WINEDEBUG=+ntdll jack_fst vst_dir/Crystal/Crystal.dll <SNIP> trace:ntdll:NtCreateFile handle=0x7f754580 access=80000000 name=L"\\??\\C:\\windows\\win.ini" objattr=00000040 root=(nil) sec=(nil) io=0x7f754584 alloc_size=(nil) attr=00000080 sharing=00000001 disp=1 options=00000050 ea=(nil).0x00000000 trace:ntdll:NtQueryInformationFile (0x78,0x7f75457c,0x7f754584,0x00000024,0x00000004) trace:ntdll:FILE_GetNtStatus errno = 13 trace:ntdll:FILE_GetNtStatus errno = 13 trace:ntdll:FILE_GetNtStatus errno = 13 Segmentation fault flash mark $ flash mark $ WINEDEBUG=+ntdll jack_fst vst_dir/SIR_1005.dll <SNIP> trace:ntdll:NtCreateFile handle=0xbfffd548 access=80000000 name=L"\\??\\C:\\windows\\win.ini" objattr=00000040 root=(nil) sec=(nil) io=0xbfffd54c alloc_size=(nil) attr=00000080 sharing=00000001 disp=1 options=00000050 ea=(nil).0x00000000 trace:ntdll:NtQueryInformationFile (0x90,0xbfffd544,0xbfffd54c,0x00000024,0x00000004) Segmentation fault flash mark $ flash mark $ WINEDEBUG=+ntdll jack_fst vst_dir/VSTMMon/MIDIMonitor.dll <SNIP> trace:ntdll:NtCreateFile handle=0x7f754580 access=80000000 name=L"\\??\\C:\\windows\\win.ini" objattr=00000040 root=(nil) sec=(nil) io=0x7f754584 alloc_size=(nil) attr=00000080 sharing=00000001 disp=1 options=00000050 ea=(nil).0x00000000 trace:ntdll:NtQueryInformationFile (0x84,0x7f75457c,0x7f754584,0x00000024,0x00000004) Segmentation fault flash mark $ Now, I don't know how to capture this point in the operation of these VSTs under the version that works. Is there a way? (Probably not...) Is this the problem, or am I fooling myself? Is this going to be enough to get Alexandre's attention? It turns out that virtuals.c was probably the most heavily edit one of the files in this set of check-ins. Seems like that might point toward some more portential for error, although why it would show up like this is way beyond my meager skills. Should I send this to Wine-dev? I'll be posting it within my bug report later this evening. Thanks, Mark _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
