On Thu, 28 Oct 2004 11:50:24 -0700, Duane Clark <dclark@xxxxxxxxxxx> wrote: > > > When the program crashes, does it dump you into the Wine debugger so > that you can get a backtrace? Unfortuantley no. I'm not strictly sure whether Wine is segfaulting, jack_fst is segfaulting, or the VST is segfaulting: flash mark $ wine --version Wine 20041019 flash mark $ jack_fst vst_dir/Crystal/Crystal.dll Segmentation fault flash mark $ I can run WINEDEBUG=+something, but it generates so much stuff that it's hard to be sure what I'm catching. I'm just starting to mess around with this. Each VST seems aq little different, so I'm trying to see what is common. > > The easiest way I find to debug is to insert lots of TRACE statements > into the code to see what is happening. By scattering them all through > the routines, and seeing what TRACEs get executed prior to the crash, > you might be able to find out exactly what line of code is causing the > crash. Though with memory corruption bugs, the corruption might have > occurred long before the crash. This makes lots of sense to me, especially since I'm not a programmer. I spent some time on the WineHQ site and in Google but didn't find exactly what the process was for adding TRACE statements. Can you provide an example I could work from? thanks, Mark _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
