You can put in some messages - in the suspect places using the
FrmCustomAlert function .. see till which point the messages pop-up .. that
will give you an ok idea of where the code is failing.

rgds

Ken Miller <[EMAIL PROTECTED]> wrote in message news:6818@palm-dev-forum...
>
> Can anyone tell me the best way to debug a program so
> that I can get the line number to narrow down the
> problem?  I am getting a memory leak problem and not
> sure how to find out where it is coming from.
>
> I am using GCC ported to Windows (0.5.0 variety) with
> the 3.1 SDK.
>
> Thanks in advance.
>
> Ken
>
>
> __________________________________________________
> Do You Yahoo!?
> Talk to your friends online with Yahoo! Messenger.
> http://im.yahoo.com
>
>
>



-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palm.com/devzone/mailinglists.html

Reply via email to