On 22 Jul 2004 at 16:04, Ben Combee wrote: > At 03:47 PM 7/22/2004, you wrote: > >The problem fails at one instruction. I have a function call that returns a > >double value to a variable declared by: > > > >double SecondFact; > > > >I initialize that with: > > > >SecondFact = 0; > > > >Now, here is the original use of the statement that causes the problem: > > > >SecondFact = (double) ParseBaseInt(dd, SecondFact, &baseErr); > > > >This statement causes a system reset. dd, SecondFact and baseErr > >are defined properly and I have even removed that function all-together > >and I still have the same error, so the function, itself, isn't the problem. > > This sounds like the perfect kind of problem to be solved by hooking a > debugger up to PalmSim and tracing at the assembly level. Determine what > instruction causes the crash, and then look at the registers to see what > kind of memory access is happening that's bad.
Unfortunately, that isn't an option. :-) The best way I can describe this is the variable SecondFact can't be assigned a value, where it is located. Other similar double type variables can. Wierd! Hopefully, someone will have a suggestion. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
