Re: Debugging a MIDServer Driver Plugin
Re: Debugging a MIDServer Driver Plugin
- Subject: Re: Debugging a MIDServer Driver Plugin
- From: Doug Wyatt <email@hidden>
- Date: Thu, 9 Oct 2003 12:27:15 -0700
I debug the MIDIServer in the same way you're describing -- I launch it
under gdb in Terminal, then launch clients.
When clients can't see any MIDI devices, are there multiple copies of
the MIDIServer process running? If so, are they owned by different
users?
Doug
On Oct 8, 2003, at 7:22 AM, Cameron Jones wrote:
It used to be (in 10.2 days, I think) I could launch MIDIServer from
Terminal, see the printf output from my driver, and MIDIServer would be
fully functional.
In my current Jaguar installation, I can launch MIDIServer from
Terminal (no
problem), I can then see my printf output (no problem), but MIDI
applications don't see any MIDI devices (big problem).
Is there a way to launch MIDIServer so that I can see my printf
output, and
MIDIServer is fully functional to the rest of the system?
Or, more simply, how can I see debug output from my MIDI driver plugin
in
vitro?
_______________________________________________
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.