Re: CoreMIDI bus error, OSStatus -10839
Re: CoreMIDI bus error, OSStatus -10839
- Subject: Re: CoreMIDI bus error, OSStatus -10839
- From: brian lee dae yung rowe <email@hidden>
- Date: Mon, 21 Apr 2003 12:27:40 -0700 (PDT)
--- Kurt Revis <email@hidden> wrote:
>
On Monday, April 21, 2003, at 08:48 AM, brian lee dae yung rowe wrote:
>
>
> I am testing the MIDI sample code provided in various published
>
> documentation,
>
> and I am receiving the following error:
>
> CoreMIDI: timeout waiting for MIDIServer to start
>
>
>
> The OSStatus code is -10839. I get this when calling each function,
>
> including
>
> MIDIRestart, MIDISend.
>
>
Run /Applications/Utilities/Console.app, and in the preferences, turn
>
on "Enable crash reporting" and "Automatically display crash logs".
>
Then start your app. It will try to start the MIDIServer process, and
>
fail (I assume because the MIDIServer is crashing). You should see a
>
window pop up with details of how the MIDIServer process crashed.
Ah, what wicked wonders lay hidden here. I've attached a crash report at the
end of the message.
>
Most likely, there is some kind of problem with a MIDI driver, which is
>
causing the crash. Try moving aside any drivers in /Library/Audio/MIDI
>
Drivers/ and ~/Library/Audio/MIDI Drivers and try again.
I should add that Midi works fine until I run my app. I have a simple app in
Max/Msp that I can send Midi messages which your fine app picks up nicely. It
isn't until I run my app that everything goes awry.
Hmm, after updating the Developer Tools, the behavior is different. Now I get
a segmentation fault. Thankfully the Midi services aren't blown away -- I can
still send from Max/Msp.
>
> I am also using a utility called MIDIMonitor, which returned a similar
>
> error,
>
> advising me to log out or restart.
>
>
Have you logged out or restarted? Also, what version of OS X are you
>
using?
Logging out fixes the problem. I'm using 10.2.5 with the latest Developer
Tools (December 2002).
>
> Am I to assume that potentially errant MIDI packets will corrupt
>
> CoreMIDI and
>
> there is no graceful recovery?
>
>
No. You're not even getting far enough to send MIDI--there is something
>
else wrong with your system.
Below is the crash report.
Regards,
brian
-----
Date/Time: 2003-04-21 15:23:01 -0400
OS Version: 10.2.5 (Build 6L29)
Host: oishi.local.
Command: MidiBroadcast
PID: 564
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0xc000cffc
Thread 0 Crashed:
#0 0x953d75ac in MIDIPacketListSize(MIDIPacketList const*)
#1 0x953d394c in MIDISend
#2 0x000035e0 in main (miditestsend.cpp:68)
#3 0x00002fac in _start (crt.c:267)
#4 0x00002e2c in start
Thread 1:
#0 0x90073c28 in mach_msg_trap
#1 0x90005f70 in mach_msg
#2 0x953ddd60 in XServerMachPort::ReceiveMessage(int&, void*, int&)
#3 0x953d1798 in MIDIInPortThread::Run()
#4 0x953d55dc in XThread::RunHelper(void*)
#5 0x90020d28 in _pthread_body
PPC Thread State:
srr0: 0x953d75ac srr1: 0x0000d030 vrsave: 0x00000000
xer: 0x20000000 lr: 0x953d394c ctr: 0x000e56f6 mq: 0x00000000
r0: 0x953d3934 r1: 0xbffff4e0 r2: 0x2800024c r3: 0xc000cff4
r4: 0x00000000 r5: 0x00000000 r6: 0x00000020 r7: 0xbffff378
r8: 0x2e202000 r9: 0xc000cfea r10: 0x00000002 r11: 0xbffff110
r12: 0x9005e2b8 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000
r24: 0x00000000 r25: 0x00000000 r26: 0xbffff6a0 r27: 0x00000008
r28: 0xbffff110 r29: 0x0981000f r30: 0x0981001d r31: 0x953d391c
=====
.
{: } the mux space conglomerate
" family values were never this good "
The New Yahoo! Search - Faster. Easier. Bingo
http://search.yahoo.com
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.