|
I have experienced this in the past. I would run a program and get unexpected results, put it in debug without recompiling or anything andall the sudden everything is fine.
The one and only time I have encountered this behaviour is when I had a bad parameter list. The caller didn't match the callee and storage was corrupted. Putting it in debug apparently re-arranged some of the internal storage in the job, giving the program the appearance of working properly. I suppose any storage corruption would result in similar behaviour.
--buck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.