[Wine]Re: WINEDEBUG for a non-descript segfault

[Mark Knecht]

On Tue, 19 Oct 2004 12:55:33 -0700, Mark Knecht <markknecht at gmail.com> wrote:
> Hi,
>    I'm loooking at a Linux program that calls WIne and then segfaults
> without any real information. Are there any debug channels that make
> most sense to try and trap in this specific case?
> 
> Thanks,
> Mark
> 

OK, so since it mentions MIDI I tried looking at the MIDI channel and got this:

flash mark $  jack_fst /home/mark/vst_dir/SIR_1005.dll 
ALSA lib pcm_hw.c:1155:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p
failed: Device or resource busy
err:wave:ALSA_WaveInit open pcm: Device or resource busy
err:midi:MIDI_AlsaToWindowsDeviceType Cannot determine the type of
this midi device. Assuming FM Synth
Segmentation fault
flash mark $ WINEDEBUG=+midi jack_fst /home/mark/vst_dir/SIR_1005.dll 
ALSA lib pcm_hw.c:1155:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p
failed: Device or resource busy
err:wave:ALSA_WaveInit open pcm: Device or resource busy
trace:midi:ALSA_MidiInit Initializing the MIDI variables.
trace:midi:ALSA_AddMidiPort OUT (0:System:kernel:0:Timer:0)
trace:midi:ALSA_AddMidiPort IN  (0:System:kernel:1:Announce:0)
trace:midi:ALSA_AddMidiPort OUT (63:OSS sequencer:kernel:0:Receiver:0)
trace:midi:ALSA_AddMidiPort OUT (128:Client-128:user:0:qjackctl:100000)
err:midi:MIDI_AlsaToWindowsDeviceType Cannot determine the type of
this midi device. Assuming FM Synth
trace:midi:ALSA_AddMidiPort MidiOut[0]name='Client-128' techn=4
voices=16 notes=16 chnMsk=ffff support=3
ALSA info: midi dev-type=100000, capa=0
trace:midi:ALSA_MidiInit End
trace:midi:ALSA_midMessage (0000, 0064, 00000000, 00000000, 00000000);
trace:midi:ALSA_midMessage (0000, 0035, 00000000, 00000000, 00000000);
trace:midi:ALSA_modMessage (0000, 0064, 00000000, 00000000, 00000000);
trace:midi:ALSA_modMessage (0000, 0001, 00000000, 00000000, 00000000);
trace:midi:ALSA_modMessage (0000, 0002, 00000000, BFFFEBAC, 00000034);
trace:midi:modGetDevCaps (0000, 0xbfffebac, 00000034);
Segmentation fault
flash mark $ 

However, SIR.dll does not, TTBOMK, use MIDI, so this seems a bit bogus. 

Another VST that does use MIDI, and fails under wine-20040914 but
works under wine-20040505 is Crystal:

flash mark $  jack_fst /home/mark/vst_dir/Crystal/Crystal.dll 
fixme:ole:CoCreateInstance no classfactory created for CLSID
{00021401-0000-0000-c000-000000000046}, hres is 0x80040154
Segmentation fault
flash mark $ 

I don't have a clue what to look at with this one. I suspect the real
failure is not MIDI related but something more basic.

2.6.9-rc2-mm4-VP-S7-UMP-noACPI
glibc-2.3.4 - NPTL
wine-20040914

Thanks,
Mark