I totally understand, but I did not discover the problem until I was well into a larger project that I could not de-construct to try to generate a reproducible sample. I am under a time pressure, decided to start using using LAZ/FPC about 3 months ago, and when I starting running the program under load, it started to die. So I cleaned up my string function calls, separated out the pchar calls, and things just magically healed themselves. The program passes ALL of my load testing and just keeps running. Do not ask me to reproduce it since I cannot and I do not dispute that in a single threaded test application, that it works. The problem is when you start building up a large pile of code and then start up the high volume testing, things really show themselves. The problem in this particular case is the the GDB back trace on segment fault was total garbage, so I cannot use that to tell you where the bug is. Trust me, I am putting my financial basis into the binary output of the FPC compiler since I can produce a much larger quantity of code faster for LInux and Mac than I can with GCC/Xcode. But for those like me, this serves as a warning to pay attention to this aspect. There is not some underlying instability, but I believe a certain combination of things causes a pointer reference that is off into la-la land. My problems were in Copy( ) and PosEx( ), nothing more. You guys rock! md On 6/11/2013 9:03 AM, Antonio Fortuny
wrote:
Hi Folks. |
_______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal