Re: [Lmuse-developer] jack midi crash

[Tim E. R. <ter...@ro...>]

On June 17, 2012 3:15:00 PM Tim E. Real wrote:
> On June 17, 2012 8:30:34 PM Robert Jonsson wrote:
> > Hi,
> > 
> > When opening a second project (probably while the old one was playing)
> > I got the following crash
> > 
> > Program terminated with signal 11, Segmentation fault.
> > #0  0x0093bae0 in MusECore::MidiJackDevice::open (this=0x9cbb328)
> > 
> >     at
> > 
> > /home/ddskrjo/dev/svn_muse/lmuse/branches/release_2_0/muse/driver/jackmidi
> > .
> > cpp:149 149           if(MusEGlobal::audioDevice->deviceType() ==
> > AudioDevice::JACK_AUDIO)
> > #1  0x002ac0a1 in MusECore::MidiPort::setMidiDevice (this=0x3bc668,
> > dev=0x9cbb328)
> > 
> >     at
> > 
> > /home/ddskrjo/dev/svn_muse/lmuse/branches/release_2_0/muse/midiport.cpp:16
> > 4
> > #2  0x002ad1c2 in MusECore::MidiSeq::msgSetMidiDevice (this=0x97a1fe0,
> > port=0x3bc668, device=0x9cbb328)
> > 
> >     at
> > 
> > /home/ddskrjo/dev/svn_muse/lmuse/branches/release_2_0/muse/midiseq.cpp:774
> > 
> > Reason being that MusEGlobal::audioDevice was 0x0, I'm not sure it is
> > save just to test for this case so I'm sending it along instead.

Strange, audioDevice should never be be NULL until shutdown.
How did it get that way? Corruption?

I tried a few tests but could not make it happen.

I'm guessing the msgSetMidiDevice call is from the readConfigMidiPort()
 during song loading but it's also called various other places.

Tim.

> > 
> > Regards,
> > Robert
> 
> Wha! That's a new one, don't think it's anything I did recently...
> Thanks good catch.
> Checking...
> Tim.
> 
>