util: stop debug.log dropping lines under concurrency (#29)

OutputDebugStringF resolved its path lazily with no lock:

    static string strDebugFile;
    if (strDebugFile.empty()) { ... strDebugFile = dir + "\\" + "debug.log"; }
    FILE* fileout = fopen(strDebugFile.c_str(), "a");
    if (fileout) { ... }

One thread could read that string while another was still assigning to it, and
at startup three threads log within milliseconds of each other. When it raced,
fopen received a torn path, returned NULL, and the `if (fileout)` dropped the
line with no error anywhere. Several threads calling fopen on the same file at
once had no protection either.

Measured over six runs, counting first-statement printfs that are unconditional
and must appear every time:

    ThreadBtfAccept started    4/6
    ThreadNostrSeed started    5/6
    btfpeers: (cached peers)   2/6

Over eight runs after the change, all three are 8/8.

This matters beyond tidiness. A missing line was read as a thread that never
started, and a real investigation was spent on it. Any reasoning of the form
"it is not in the log, so it did not happen" was unsound against this build.

Path resolution and the write now share one critical section. The rest of the
function already had its own for the OutputDebugString accumulation path; only
the file half was unguarded.

0 files changed, 0 insertions, 0 deletions