This seems to be a team project, with "junior" programmers involved. Since
the known bug (reference to invalid memory areas) is so blatent, I would
recommend code walk-thrus and other peer-review procedures be installed.
Make sure your entire team is using maximum error reporting using the
"-Wall"
The 68k really doesn't care about reading the wrong address, although you
could get an alignment fault by reading from an odd (as opposed to even)
address. I can't think of any I/O ports that will object to a random read,
although you could maybe clear some condition that hadn't been serviced yet.
ROTECTED]]
Sent: Wednesday, February 12, 2003 2:56 PM
To: Palm Developer Forum
Subject: RE: Opinions on Expectation of problems with a known invalid
global data access.
You never know if the errant read will cause a problem. You really
should protect against doing that. Is it possible to mess up
M
To: Palm Developer Forum
Subject: Re: Opinions on Expectation of problems with a known invalid
global data access.
Doesn't this amount to reading a value from an ill-defined location then
taking an action based on the value? Sounds like trouble brewing...
Dennis Leas
---
tor), will leave our app or the OS in a bad state
Kevin
-Original Message-
From: Dennis Leas [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 12, 2003 11:53 AM
To: Palm Developer Forum
Subject: Re: Opinions on Expectation of problems with a known invalid
global data access.
Doesn
"Palm Developer Forum" <[EMAIL PROTECTED]>
Sent: Wednesday, February 12, 2003 2:37 PM
Subject: Opinions on Expectation of problems with a known invalid global
data access.
> Our application handles a non-global launch code (via an alarm). Someone
has inadvertently added a global flag
Our application handles a non-global launch code (via an alarm). Someone has
inadvertently added a global flag to the code that handles the launch code. The code
in question only READS the global - it does not change it. I have demonstrated to
myself and my colleagues that this code cases a B
