On Sun, 17 Oct 2004 10:31:42 -0700, Duane Clark <dclark@xxxxxxxxxxx> wrote: > Mark Knecht wrote: <SNIP> > > with error messages from > > (I think) Wine: > > > > err:seh:EXC_DefaultHandling Unhandled exception code c0000005 > > > > First, do you agree this message is in fact coming from Wine? That's a > > guess on my part, except I've seen the 'code c0000005' think in a lot > > of Windows driver failures over the years so I presume it's coming up > > to the surface through that path. > > Yes, it is a Wine generated error. It is coming from here: > http://source.winehq.org/source/dlls/ntdll/exception.c#L207 > > > > > What is 'seh'? > > Wine has the concept of "debug channels". "seh" probably stands for > mumble exception handler, or something like that. Take a look at the > bottom of: > http://www.winehq.org/site/docs/wine-user/x2192 > > It is a very convenient way of debugging Wine. > That's really interesting. Thanks! It looks, from the links you pointed me toward, that I'd want to run some form of: $ WINEDEBUG=warn+heap wine program_name However, for me to run Battery as a VST under Wine I do not run Wine directly, but rather I run a program called jack_fst which runs Wine for me. Does this imply that I'd have to change the jack_fst code to call wine in a different way? Of can I set WINEDEBUG in a terminal and then run jack_fst from the same terminal and accomplish the same thing? Thanks very much, Mark _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
