From: [EMAIL PROTECTED]
Subject: Re: Palm Debugger Stub
>My other option is to simply have a debug version of my Smalltalk VM that
>can talk to the PC and provide variable info, provide step functionality,
>and modification of code while debugging. This would be good and all, but
I
>think the stub approach would be easier to do.
Personally, this is the way I'd go. Since you say "...simply have a debug
version...", then it shouldn't be too hard to do. Poser and the Palm OS
take
this approach when talking with external debuggers.
- -- Keith Rollin
- -- Palm OS Emulator engineer
Eric:
I agree that that is the approach taken with existing debuggers. One of the
problems is that the code, compile, debug cycle gets very tedious after a
while. Especially when the debugger works as well as CWs ;-> I know this
is something most of you have had to deal with, but I am trying to avoid
this. Most Smalltalk environments are dynamic and support changing of code
incrementally. This reduces the whole cycle time. Think about it, if I
could change a single function and continue, it would take a lot less time
to build applications. This what I am trying to achieve.
Now, I did oversimplify with my statement of "simply have a debug version".
It would require a lot more work on our part than building a stub. In order
to reduce the size of an application, the runtime environment is more static
than the development environment. It would be a lot more work than
"simply". Any ideas on possible pitfalls ?
