Ben Combee,
On Wed, 26 Apr 2000 16:18:07 -0500, you said:
>
> The really useful part is in the other two panes -- one shows all the local
> variables active before the function call, and the other shows where in the
> source the call occured.
the only problem is, it only shows the place in YOUR program where there
is a crash. It only shows YOUR variables. Since the problem seems to
be inside PalmOS call itself these windows don't tell me anything except
what the variables are just before the call. Those I have checked again
and again. They are valid. But for some dumb reason it still crashes in
the OS.
How in the world can I crash the OS as long as I am passing valid
pointers? Why does it only crash on my poor helpless program. Is there
some way to use the stack window to find out if the pointer is being
safely passed to the API function that I am calling?
Is there some way to get a hold of the source code for the PalmOS call
in question so I could find out exactly which part of it is messing up?
derik
email: [EMAIL PROTECTED]
WWW: http://www.pobox.com/~derik
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
