debugging plugins w/CodeWarrior

[Matthew D Moss]

I am working on a project that uses plugin modules.  These modules are
single 'code' resources that are loaded and locked in memory by the main
application.  A single entry point called "MTPluginMain" provides access
much like "PilotMain" does for applications.

But I can't debug these with CodeWarrior, or at least not with a default,
basic setup.  Is there any way to convince/persuade/fool CodeWarrior into
debugging these sorts of plugins?

---- --- -- -
Matthew D Moss
[EMAIL PROTECTED]