Re: Debugging a MIDServer Driver Plugin
Re: Debugging a MIDServer Driver Plugin
- Subject: Re: Debugging a MIDServer Driver Plugin
- From: Kris Daniel <email@hidden>
- Date: Wed, 8 Oct 2003 08:03:32 -0700
Try using /Applications/Utilities/Console. There may be a few messages
in there from other applications, but that's where your standard
printf()s go when they're not run from Terminal. I've had to use this
for debugging my MIDI driver in a release/deployment mode build, so I
know it's possible.
Kris Daniel
Line 6, Inc.
On Wednesday, October 8, 2003, at 07: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?
Thanks in advance!
Cameron Jones
Salem Technology Associates
_______________________________________________
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.
_______________________________________________
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.