You can also open one of your source files **while the debugger is running**
and set break points in places you need.
JB @ PalmSource
on 10/9/02 7:32 PM, Gavin Maxwell at [EMAIL PROTECTED] wrote:
> I've never used that option, however I think you'll find it easier if you
> manually set breakpoi
At 19:55 2002-10-9 -0400, you wrote:
>I use breakpoints all the time. A 'break' is more useful when your program
>is getting stuck in an endless loop and its not immediately clear where it
>is. I'm using Gremlins and its happening after 20,000 or so events, so its
>takes a while to track down an
I use breakpoints all the time. A 'break' is more useful when your program
is getting stuck in an endless loop and its not immediately clear where it
is. I'm using Gremlins and its happening after 20,000 or so events, so its
takes a while to track down an endless loop using only breakpoints. If
I've never used that option, however I think you'll find it easier if you
manually set breakpoints where you want your app to stop, then you can step
through easily. To set a breakpoint click in the far left portion of the
source window - a red dot should appear. Alternatively you can using F9 (PC
When debugging, either with or without gremlins running, I'd like to be able
to stop the run at the current line of execution and start stepping through
my app. "Debug > Break" is always off (grayed out). How do I activate it?
I looked through preferences, but didn't see anything.
Thanks!
Rich
