'stdin' oddity

[Michael Vance]

glibc,

I have an odd situation where a call stack of the form:

__pthread_mutex_lock
__flockfile
_IO_vfprintf
printf

is causing a segfault, maybe because the _lock pointer in stdout is
NULL. Checking against some other programs I have, the _lock pointer
is indeed valid. I've attempted to single out where an assignment or
overwrite could possibly be happening, but it appears that even at
_init the value is NULL. I then noticed that I have a data member in
my binary that might clash:

address@hidden build]$ nm tribes2-debug | grep "stdout"
086612e0 D _IO_2_1_stdout_
086a20e4 B stdout@@GLIBC_2.0

However I have no idea where this is coming from, or if it in fact is
the source of the problem. I'm looking for some advice as to where I
should go next in fixing this. My system is currently using
glibc-2.1.1, which I understand is not current, but because of
incompatabilities between various glibc versions this is the only one
we can use for building usable binary applications. Any help is
appreciated.

Thanks,

m.

-- 
Programmer             "Ha ha." "Ha ha." "What are you laughing at?"
Loki Software                      "Just the horror of being alive."
http://lokigames.com/~briareos/                   - Tony Millionaire