[bf1942] crashes on connect/mapchange...

[Ryan C. Gordon]

> glibc-2.2.4-31

I wonder if it's a glibc incompatibility...

> I did a "ps -ef" and noticed that the first process spawns the second, which
> in turn spawns the third:
>
> tom       1441  1060 10 14:13 pts/5    00:00:35 ./bf1942_lnxded
> tom       1442  1441  0 14:13 pts/5    00:00:00 ./bf1942_lnxded
> tom       1443  1442  0 14:13 pts/5    00:00:00 ./bf1942_lnxded

Under Linux, each thread is a process.

The first thread is the main program. The second one is the "monitor"
thread (which glibc spawns when you spin your first thread), and the third
is the socket i/o thread, which does all the talking to clients. The
firsst thread should use significantly more CPU time than the other three.

> Perhaps that's due to the constant STUB messages that repeat.  When the
> server tries to change maps on its own, the bf1942_lnxded processes die and
> are replaced by new ones before the server crashes.

The server restarts itself (literally...with an execl() call) between each
map...the win32 version does this, too. (Actually, the client does, also,
now that I think about it).

--ryan.