In response to a question I posted a while back, I received the following
response:
>If you're using CodeWarrior R5 (and above) you can debug your plug-in!
>Follow these steps to debug it:
> ? If your plug contains only one target , switch to "Targets" tab in the
>Plugin.mcp window & from the "Projects" menu select "Create New Target."
>cloning your main target. Add a "- Debug" suffix to new target's name.
> ? Switch to the Debug' target (you created above).
> ? From the "Projects" menu select "Enable Debugger".
> ? Open the project's preferences.
> ? In the "68K Linker":
> ? Set the "MacsBug Symbol" to "New Style"
> ? Check "Generate SYM File"
> ? Check "Generate A6 Stack Frames"
> ? In "Debugger Settings" set the "Program to Launch for." to DeskMate.prc.
> ? From the "Projects" menu select "Debug" (F5).
I've tried most of these things with no luck. I don't know what
DeskMate.prc is, so I used the name of my main Palm app. And I didn't
create a new target with "- Debug" appended to the name, since my target was
already debug. I don't expect either of these things should matter in
determining source level debug capability.
Any ideas? To restate my problem, I can't source debug my plugins. My
plugins are 'code' resources, loaded and locked into memory, with an entry
point of __Startup__, and are probably (but not necessarily) in separate
files from the main app. (I've tried integrated and separate plugins
without much difference either way. I have a multi-target project covering
both app and plugins, so I don't know if that matters.)
---- --- -- -
Matthew D Moss
[EMAIL PROTECTED]
