> > you maybe corrupting the stack somewhere, and, as a result.. corrupting
> > the "program counter".. and wola.. try storing your string in a resource
> > instead of as a "local" object in the application..
> >
> > you are messing with too much memory, and it just cannot handle it.
> >
> > if you changed yout string to "jjjjjjjjjjjjjjjjjjjjj", then i bet your
> > error would be "0x70707070" :P - just a small hunch i have :)) try it.
> > PilRC allows you to create a string resource, and you should be able to
> > do the same in the Code Warrior environment.
> >
> > [EMAIL PROTECTED]
>
>
> Thanks guys. Silly me, I should have known where that 0x69 was coming
> from. Actually, changing the string to "jjjjjjjjjjjjjj" gives 0x6A, not
> 0x70 -- it's hex, after all.
thats alcohol + hangover for you :))
> Funny thing, that. I originally coded for Linux, using printfs for
> debugging purposes. When I ported to Palm, I just left the printfs in
> the code and the compiler didn't complain even though I wasn't including
> the UNIX stdio.h. On a Palm, the printf just dumps a string onto the
> screen without regard to your application's UI. printf has been a good
> debugging tool up until now.
if you want to test it.. try this:
StrPrintF(str, "...", ... );
ErrFatalDisplayIf(1, str);
i assume, you just want to see the "format" - using the "dialogs"
is a good technique.. just "continue" when done.
// az "no more beer for me"
[EMAIL PROTECTED]
http://www.ardiri.com/ <--- free games!
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
