In trying to print debugging information to diagnose a problem with an rpc call, I stumbled upon a printf-of-death. I have narrowed down at least two independent surprise behaviors with printf:

• printf's format string argument cannot exceed 1000 characters.
• printf's output length cannot exceed 1023 characters.

These lead not just a "Crash in script".
In Windows this is a hard crash-to-desktop. A message box says "Zorro Automaton has stopped working".
In wine i get
wine: Unhandled exception 0xc000000d in thread 18 at address 0x514658 (thread 0018), starting debugger...
winedbg: Internal crash at 0x7ed2b0b5

Verbose/diag log is empty.

Example of first bug (Crash)

Please let me know if you need a script example for the first one. (Just print a string literal longer than 1000 chars and you'll see it.)

Change
response[1023] = 0;
to
response[1022] = 0;
= no crash

strlen is not affected. So I can see that response is 1024 bytes but trying to print it kills me.

Feature Request
strncpy , snprintf, etc.

Printf prints in the message window and thus must not exceed its buffer size - I believe it's indeed 1024 characters. I have no idea why this was omitted in the manual, but I'll add it.

Using strncpy etc. is up to you. The C library functions are described in all C books. But you must add a header - look into the stdio.h header as an example.

If you had snprintf you could replace the formatted output with a truncated output or a warning message instead of crashing.

From my perspective, I had a crash bug in my Strategy. I added a printf to see what was happening. Then I had two crash bugs.

Yes, I've sent a request to fix the bug by issuing an error message.