Thanks for pointing that out. I was using the debugger, it's just new to me
so I haven't learned some of the commands yet. Gdb is pretty cryptic.
Unfortunately, the only reason I cared about the return values was that
later in the code I was getting an exception when I tried to lock and read
the memory I allocated earlier. I have an event handler for a trigger press
where I am locking and trying to read the strings that I had initialized
earlier. I know its tough to guess without seeing the code, but it's on my
home machine. Any thoughts?
<[EMAIL PROTECTED]> wrote in message news:914@palm-dev-forum...
>
>
>
> >...I just didn't want to mess with the debugger).
>
> Well, you should. It's your homebrew display routines that are messing you
up.
> In the line:
>
> StrPrintF(test,"%d, %d ,%d",h,j,i);
>
> You're pushing "h" onto the stack, and then telling StrPrintF to display
it with
> "%d". The former is a 32-bit value, the latter expects a 16-bit value.
Because
> of the disparity in sizes, your printing routine gets all "out of whack"
(that's
> a technical term).
>
> -- Keith Rollin
> -- Palm OS Emulator engineer
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
