[fpc-devel] 019605: Safety check for "const s: string" (similar to Range or Overflow checks)

Marco van de Voort marcov at stack.nl
Thu Jun 23 22:12:14 CEST 2011

In our previous episode, Jonas Maebe said:
> > It may bne rare, sure. But it is also one that is very hard to find. Because code like this may run without crash, for a long time, and by the time one notices it, it is hard to track. And *if* const param are used, it is easy to sneak in, even if the author is available of it (which I believe very very few people are)
> FWIW: Valgrind should also be able to identify such errors (of course, it requires that you are on a platform that's supported by Valgrind)

And the problem with the profiler is often that their slowness (both startup
and during production run) prohibits testing at the client's setup. Moreover
their operation requires skill.  I've such problems both with AQTime and
even with remote debugging Delphi apps.

While a binary with certain checks compiled in can be run by the client,
though of course it must be possible to create some kind of log in such

More information about the fpc-devel mailing list