• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: LAM HELP HELP HELP (Repost) Midi server crashing
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LAM HELP HELP HELP (Repost) Midi server crashing


  • Subject: Re: LAM HELP HELP HELP (Repost) Midi server crashing
  • From: Cyril Blanc <email@hidden>
  • Date: Thu, 15 May 2003 06:53:01 +0200

On 12/05/03 21:25, "Doug Wyatt" <email@hidden> wrote:

> On Friday, May 9, 2003, at 22:19 US/Pacific, Cyril Blanc wrote:
>> Hello
>>
>> Now I cannot launch any more any midi application without having :
>>
>> May 10 06:15:15 Cyril-Blancs-Computer crashdump: Crash report written
>> to:
>> /Users/cyrilbla/Library/Logs/CrashReporter/MIDIServer.crash.log
>>
>> WHAT CAN I do to start with a clean Midi section
>> CoreMIDI: timeout waiting for MIDIServer to start
>>
>> -----------------------------------------------------------------------
>> -----
>> -----------------------------------------------------------------
>> Date/Time: 2003-05-10 06:15:15 +0200
>> OS Version: 10.2.6 (Build 6L60)
>> Host: Cyril-Blancs-Computer.local.
>>
>> Command: MIDIServer
>> PID: 512
>>
>> Exception: EXC_BAD_ACCESS (0x0001)
>> Codes: KERN_INVALID_ADDRESS (0x0001) at 0x01173580
>>
>> Thread 0 Crashed:
>> #0 0x901a3b58 in __CFDictionaryFindBuckets1b
>> #1 0x901315c4 in CFDictionaryGetValue
>> #2 0x90131168 in __CFStringMakeConstantString
>> #3 0x00213184 in SerialDevice::SerialDevice[unified](unsigned)
>> (SerialDevice.cpp:68)
>> #4 0x002132b0 in SerialDeviceManager::ServicePublished(unsigned)
>> (SerialDeviceManager.cpp:60)
>> #5 0x00212094 in IOServiceClient::ServicesPublished(unsigned)
>> (IOServiceClient.cpp:177)
>> #6 0x00211ff0 in IOServiceClient::ScanServices()
>> (IOServiceClient.cpp:150)
>> #7 0x00214470 in
>> SerialMIDIDeviceManager::SerialMIDIDeviceManager[unified](SerialMIDIDri
>> verBa
>> se*, OpaqueMIDIDeviceList*) (SerialMIDIDeviceManager.cpp:67)
>> #8 0x00214a60 in SerialMIDIDriverBase::Start(OpaqueMIDIDeviceList*)
>> (SerialMIDIDriverBase.cpp:79)
>> #9 0x90ceb87c in DriverTable::StartMIDI()
>> #10 0x90ce56e4 in SetupManager::Install(MIDISetup*, bool)
>> #11 0x90cf0118 in MIDIServerRun
>> #12 0x00002904 in 0x2904
>> #13 0x0000269c in 0x269c
>> #14 0x0000251c in 0x251c
>>
>> Thread 1:
>> #0 0x9003eaa8 in semaphore_wait_signal_trap
>> #1 0x9003e8c4 in _pthread_cond_wait
>> #2 0x90cee3d4 in XMutex::Wait()
>> #3 0x90cec364 in Task::Run()
>> #4 0x90ce16f0 in Scheduler::Run()
>> #5 0x90ced050 in XThread::RunHelper(void*)
>> #6 0x90020d48 in _pthread_body
>>
>> Thread 2:
>> #0 0x90073c48 in mach_msg_trap
>> #1 0x90005f90 in mach_msg
>> #2 0x901489f0 in __CFRunLoopRun
>> #3 0x90180f58 in CFRunLoopRunSpecific
>> #4 0x90d07a1c in DriverIOThread::Run()
>> #5 0x90ced050 in XThread::RunHelper(void*)
>> #6 0x90020d48 in _pthread_body
>>
>> PPC Thread State:
>> srr0: 0x901a3b58 srr1: 0x0000d030 vrsave: 0x00000000
>> xer: 0x20000000 lr: 0x901a3b1c ctr: 0x90000f00 mq: 0x00000000
>> r0: 0x00003580 r1: 0xbffff9d0 r2: 0x44000280 r3: 0x38dbdd60
>> r4: 0x00000080 r5: 0xb1b28034 r6: 0x80808080 r7: 0x0000000f
>> r8: 0x4a2bdd60 r9: 0x71b7bac1 r10: 0x00000063 r11: 0x00001000
>> r12: 0x90000f00 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
>> r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
>> r20: 0x00000000 r21: 0x00000000 r22: 0x00056c64 r23: 0x01170000
>> r24: 0x00000ac1 r25: 0x00000d60 r26: 0xa1b1c1d3 r27: 0x0021d81c
>> r28: 0x00056c40 r29: 0x00000fff r30: 0x00000d60 r31: 0x901314d4
>
>
> I tried this with the sample serial MIDI driver source, and could not
> reproduce it.
>
> Two things to try:
> [1] temporarily remove all other MIDI drivers from your system (just
> hide them in other folders), including:
> /System/Library/Extensions/
> AppleMIDIUSBDriver.plugin
> AppleMIDIFWDriver.plugin
> /Library/Audio/MIDI Drivers
> ~/Library/Audio/MIDI Drivers
>
> [2] set aside ~/Library/Preferences/ByHost/com.apple.MIDI.*.plist
>
> Do either of these make the symptoms stop?
>
> Doug
>
Hello Doug

I have manage to reproduce it ; simply boot with your serial and USB midi
interfaces Powered off.

I am stuck again, replacing StealthMIDIDriver.plugin does not help any more
now !

Renaming "~/Library/Preferences/ByHost/com.apple.MIDI.*.plist" to
""~/Library/Preferences/ByHost/cyril com.apple.MIDI.*.plist" did not do
anything

It is not possible to move

> /System/Library/Extensions/
> AppleMIDIUSBDriver.plugin
> AppleMIDIFWDriver.plugin

Thanks in advance.

Best regards

Cyril Blanc
France

If you want to be sure I read your answer leave my name in it !
Spam mails are directly going to trash
_______________________________________________
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.

  • Follow-Ups:
    • load file
      • From: "aNt" <email@hidden>
    • Re: LAM HELP HELP HELP (Repost) Midi server crashing
      • From: Kurt Bigler <email@hidden>
References: 
 >Re: LAM HELP HELP HELP (Repost) Midi server crashing (From: Doug Wyatt <email@hidden>)

  • Prev by Date: Re: Slider values on an Input Volume(Gain) Control
  • Next by Date: Re: Transport start/stop for Effect Units needed
  • Previous by thread: Re: LAM HELP HELP HELP (Repost) Midi server crashing
  • Next by thread: Re: LAM HELP HELP HELP (Repost) Midi server crashing
  • Index(es):
    • Date
    • Thread