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).
? That's it!
Ramel Levin
CTO
The PalmMate Team
Gotta Palm? Gotta visit www.PalmMate.com
----- Original Message -----
From: Matthew D Moss <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 04, 1999 6:27 AM
Subject: Re: debugging plugins w/CodeWarrior
> >>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?
> >
> >Have you got the "IDE Preference->Debugger->Global Settings->Don't step
> >into runtime support code" checkbox off?
>
> Yes, the checkbox is off.
> Sorry, I should have been more specific in my original post. I'd like to
be
> able to SOURCE debug the plugin. I can debug the 68k asm, but it's slower
> and my memory of the 68k architecture is a bit fuzzy.
>
> ---- --- -- -
> Matthew D Moss
> [EMAIL PROTECTED]
>
>
>
>
