[missing-sync-palmos-dev-talk] Debugging the Carbon Sample Conduit

[Scott Gruby]

On Jun 25, 2006, at 12:01 PM, Michael Lutz wrote:

> Hello,
>
> first of all: I am really now to conduit development on the Mac, so  
> I hope the question is not already answered in some FAQ somewhere I  
> don't know of.
>
> What I am trying to do is to debug the Carbon Sample Conduit I have  
> downloaded form the Mark/Space website (thanks for providing those  
> samples and documentation btw.!!). More precisely I am trying to  
> run into a breakpoint in the OpenConduitCarbon function. I followed  
> the instructions from the "Developing Palm OS Conduits for PowerPC  
> and Intel Macs Using XCode" paper:
> - Setting the link for the executable to the /Library/.../Palm  
> HotSync/Conduits/
> - Creating the custom executables (UI and Conduit Manager)
> - writing the defaults for debugging ("defaults write  
> com.marksapce.missingsync.palmos debugConduits -bool YES" I did  
> also write to com.markspace... since I did not know if maksapce was  
> a typo)
>
> Upon starting the debugger I can see that MissingSync is launched,  
> I can get a short glimpse of the syncing window (that with the  
> progressbar) and then I get the following error message:
> <Picture 1.png>
>
> This happens only if I am trying to debug, not during a normal  
> sync. The only active (selected in the conduit prefs) conduit is  
> the Sample MachO Conduit.
>
> Any help is greatly appreciated! :-)
>

Everything you're doing appears correct. However, if any component is  
running when you do "defaults write com.marksapce.missingsync.palmos  
debugConduits -bool YES", it might be overwritten. The easier thing  
to do is to hold down the option key when selecting Preferences from  
the Missing Sync menu and turn on Debug Conduits, if it isn't already  
chosen. The error message you're getting, you shouldn't get if you  
have the Transport Monitor running; this is done by selecting one of  
the connection types in the user interface (USB, Bluetooth or  
Network). I just tested things and only got the error message you got  
when I hadn't selected USB as a connection type.

--
Scott Gruby
Mark/Space, Inc.
<http://www.markspace.com/>

Please visit <http://www.markspace.com/support/> for assistance with  
Mark/Space products.