Hi community
this is the second time I write this message, the first one completed
with BSOD :)
I'm running into problems with the new Serial Manager, don't blame me
this's not for this thread, because from what I see... it can be OS bug.
I have a fairly simple code opening serial manager, send 2 bytes and try
to read 1, something like that:
void test()
{
char tmp[6];
int result;
tmp[0]=0x0d;
tmp[1]='v';
SrmSend(...);
SrmReceive(ref,tmp,1);
result=tmp[0];
}
so... this works on everything but OS5 devices - tested on T&C, on OS5
the device resets itself. Strange. If I change it to use old serial
manager it works... but now I NEED the new one and don't know what to do.
I outputted the &tmp before the function and after it using global buffer
for the received data... sometimes the address of the tmp changes...
local stack/heap corruption? Interesting, when using global buffer
allocated with MemPtrNew all's ok. But I have ~150 functions using such a
small local buffers to send/receive, don't want to change them all!
Anyone else experienced this, and should this be reported as a OS bug?
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
