What if the two programs [A & B] that were running were reading the number as "next to be used", and functioned properly. But, a third program [C] interpreted the data area as "last used". That would also cause the problem.
For example, program A ran successfully, and then B ran successfully. When B completes, the data area contains 5, meaning the next use of the data area would be to indicate "use 5 next".
Then program C runs, and the logic thinks 5 was last used, so program C increments the data area, uses 6, and puts 6 in the data area [last used]. Then program A or B run again, and see the 6. They interpret the 6 as the next to be used, and cause the crash, because program C has already used 6 because it's data area access logic is not the same.
I recently had this happen, and it is fresh in my mind.
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
