Very well, if this would be possible. Right now I have no idea how to print
something like the above. I made Tomas Hozza's test with valgrind and wget
having debug info. I got 18x (out of 20x) SIGBUS, but on completely different
places in the code. Within the misuse test situation, SIGBUS could occur at
any place where memory access (read or write) allocated by wget_read_file().
Absolutely randomly / unpredictable if an outside process changes the file
size and/or content at the same time.
And SIGBUS could also occur out of any other reason (e.g. real bugs in Wget).