Click to See Complete Forum and Search --> : Developer needs help


75spyder
06-20-2004, 08:38 AM
Hello, I'm posting this message for a developer who is trying to write his palm GPS software to work with the iQue. The basic issue is that the device crashes when the software starts "seeing" the Garmin GPS protocol. Here's his latest message:

"I've the traced the crash problem to a single line that simply divides a variable by a non-zero constant. It seems to be either a compiler bug or an error in the PalmOS on the iQue. It does not occur under the iQue simulator."

Anyone here who developed software for the iQue can help him out?

Best Regards

Steven
sw317@hotmail.com

JMckie
06-20-2004, 08:44 AM
Can you get him to post the portion of code thats crashing?

The last thing I would suspect is OS problems or compiler problems. That line is probably a red herring and some address space corruption has happened beforehand.

How is he tracing the problem if it does not occur in the Palm simulator? If he has managed to run the debugger on the iQue device itself, I'd be very interested to know how to do that.

I'm sure Bokkie will chime in later as one of his hobbies is to find new ways of crashing the iQue :)

Bokkie
06-20-2004, 12:16 PM
Originally posted by JMckie
I'm sure Bokkie will chime in later as one of his hobbies is to find new ways of crashing the iQue :)

That's no maybe!

I'm an expert on crashing iQues. I've hosed more memory these past two weeks than I thought was possible. The problem with the simulator is it is not a ROM so memory mapping is very different to the iQue hardware. I know, I've had this problem where the simulator told me one thing and the iQue another.

As J has suggested, you are probably doing a "bokkie" in your app and you've buggered something elsewhere most likely. You might need to go back through the app and check all variables are correct in function calls and make sure you are not writing beyond the mamximum length of arrays, etc. It can be painstaking to do but possibly add some dummy code around the statement in question. If he is hosing memory, adding extra code around might leave the statement you are interested in intact. There is no guarantee that will work though.