Re: Midi Plugin
Re: Midi Plugin
- Subject: Re: Midi Plugin
- From: Kurt Revis <email@hidden>
- Date: Mon, 8 Jul 2002 15:24:17 -0700
On Monday, July 8, 2002, at 07:00 AM, Puneet Jain wrote:
I'm new to Mac OS X driver development. I have created a Midi Plugin
but don't know how to debug it ?
MIDI "drivers" are different from most other drivers on Mac OS X. They
are just plugins (shared libraries) which run inside of the MIDIServer
process. Normally, CoreMIDI starts the MIDIServer the first time an app
calls MIDIClientCreate(). However, you can run the MIDIServer yourself,
if you like.
In Project Builder, select your plugin target, go to the Executables
tab, and set
/System/Library/Frameworks/CoreMIDIServer.framework/MIDIServer as the
executable. Then when you run or debug, the MIDIServer will run. If
your plugin is in the right place, it will get loaded by the MIDIServer,
and then you can debug it (set breakpoints in it or whatever).
Alternatively, you can 'gdb
/System/Library/Frameworks/CoreMIDIServer.framework/MIDIServer' on the
command line, or use gdb to attach to an already-running MIDIServer
process. See the gdb documentation for more help on this.
Also how can I create .sym file for that plugin and do source level
debugging ?
In Mach-O, debugging symbols are stored in the executable itself, not in
a separate file. So if you're building your plugin from Project Builder,
you don't need to do anything special--the debugging symbols will
already be there.
--
Kurt Revis
email@hidden
_______________________________________________
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.
| References: | |
| | >Midi Plugin (From: Puneet Jain <email@hidden>) |