Florian-Wolfgang Stock <[EMAIL PROTECTED]> writes:
> The line Making trouble is:
> MemMove(&variable2, recordPtr, sizeof(MyStructType));
> it changed the value of variable1 instead of variable2 (which contents
> remained untouched).
I know analyzed it a bit more with the debugger and I am getting really
desperate.
(myMemMove is just a wrapper for debug purpose):
gdb-output:
124 recordPtr = MemHandleLock(recordHandle);
(gdb) step
125 myMemMove(&kampf, recordPtr, sizeof(Kampf));
(gdb) step
Breakpoint 1, myMemMove (target=0x50f0, source=0x42ec0, length=8)
85 MemMove(target, source, length);
(gdb) print &kampf
$20 = (struct <unknown> *) 0x65a98
(gdb) print &anzahlW
$21 = (unsigned short *) 0x50f0
that means the parameter "&kampf" to MemMove isnt't "&kampf" ,
but "&anzahlW". If I change before the MemMove call target to 0x65a98 (the
address the debugger gives me for "kampf"), I got an error message, indicating
that I am accessing storage ram.
So why is the struct placed in storage ram, and why does &kampf resolv to a
wrong value? I am still thinking that I am missing something with the
multi-section (maybe the variable references are just local to the section --
don't know, I didn't read anything about it in the multi-sec documentation).
--
int m,u,e=0;float l,_,I;main(){for(;1840-e;putchar((++e>907&&942>e?61-m:u)
["\t#*fg-pa.vwCh`lwp-e+#h`lwP##mbjqloE"]^3))for(u=_=l=0;79-(m=e%80)&&
I*l+_*_<6&&26-++u;_=2*l*_+e/80*.09-1,l=I)I=l*l-_*_-2+m/27.;}
--
For information on using the Palm Developer Forums, or to unsubscribe, please
see http://www.palmos.com/dev/support/forums/