This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: [briareos@lokigames.com: 'stdout' oddity]


On Mon, Oct 09, 2000 at 04:22:51PM -0700, Michael Vance wrote:
> I haven't gotten a reply from the glibc people about this yet, so I'm
> wondering if perhaps a gcc person has any clue why the compiler
> (though I imagine it's more the linker here) is causing this to
> happen? This is a complete show stopper for me right now :(
> 
> Thanks,
> 

If you can create a testcase, I will take a look. I suspect it is
a libio binary compatility bug and has been fixed since then.


H.J.
---
> m.
> 
> ----- Forwarded message from Michael Vance <briareos@lokigames.com> -----
> 
> From: Michael Vance <briareos@lokigames.com>
> To: bug-glibc@gnu.org
> Subject: 'stdin' oddity
> X-Mailer: Mutt 1.0.1i
> Date: Mon, 9 Oct 2000 12:11:45 -0700
> 
> 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:
> 
> [michael@namaste 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
> 
> _______________________________________________
> Bug-glibc mailing list
> Bug-glibc@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-glibc
> 
> ----- End forwarded message -----
> 
> -- 
> Programmer             "Ha ha." "Ha ha." "What are you laughing at?"
> Loki Software                      "Just the horror of being alive."
> http://lokigames.com/~briareos/                   - Tony Millionaire

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]