I use DebugStr on the Mac as the only point of debugging.
Björn
Phil M wrote:
There are three problems that I am having with CodeWarrior 9.2.
1. Working with a Carbon build plugin, there is always a SYM file
generated at the same time. Since I have the build directory set to
the REALbasic 2006 R3 plugins folder and REALbasic to auto-launch,
both the Plugin and the SYM file are launched. Immediately after I
run the CodeWarrior debugger it stops with an error that the SYM file
is not a valid plugin. For now, all I need to do is click the
continue button, but I would prefer to disable output of the SYM
file. Is this possible?
2. I have not been able to get CodeWarrior to break into the debugger
using breakpoints when using the plugin in the REALbasic debugger. Is
CodeWarrior suppose to be able to break when you debug a REALbasic
app? At this point, I can only use the minimal information in the OS
X crash log to determine where my plugin is breaking.
3. To make it a lot easier to determine where my function is
crashing, what kind of logging system can I use? Is there something
similar to System.DebugLog?
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
