This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: [vesuri@jormas.com] libc/1954: glibc 2.2 getpwuid segfaults on m68k when >1 entries in /etc/passwd
- To: Vesa Halttunen <vesuri at jormas dot com>
- Subject: Re: [vesuri@jormas.com] libc/1954: glibc 2.2 getpwuid segfaults on m68k when >1 entries in /etc/passwd
- From: Andreas Schwab <schwab at suse dot de>
- Date: 13 Dec 2000 14:33:14 +0100
- Cc: Andreas Jaeger <aj at suse dot de>,libc-alpha Mailinglist <libc-alpha at sourceware dot cygnus dot com>
- References: <Pine.LNX.4.30.0012131132380.6708-100000@tikka.tki.jklmlk.fi>
Vesa Halttunen <vesuri@jormas.com> writes:
|> Hi,
|>
|> On 13 Dec 2000, Andreas Jaeger wrote:
|> > I do suspect a compiler bug here since it works on all other systems.
|>
|> This may well be true.
|>
|> > Vesuri, which compiler are you using?
|>
|> I'm using GCC 2.95.2. I tried to go back to egcs 1.1.2 since I built a
|> working glibc 2.0.7 with it but this wasn't that easy due to changes in
|> the C++ library (type streampos has changed so that programs handling it
|> as an integer instead of a structure won't build...). Building a compiler
|> on a 40MHz system takes quite a while so I didn't bother to mess with it.
|> :)
|>
|> If I find a pre-built egcs 1.1.2 for m68k I could try it out to see if
|> GCC 2.95.2 really is causing the problem. I wonder who might have
|> knowledge concerning GCC on m68k - this might even be a known bug? If
|> there are any m68k-related patches for 2.95.2 where would I find them? I'd
|> rather use 2.95.2 than egcs 1.1.2 IF I can get 2.95.2 working (if it is
|> broken). 2.95.2 has seemed to compile other stuff just fine on m68k
|> though.. So - who might know more about this? Finding m68k-related
|> material is pretty hard these days..
I cannot reproduce that with gcc 2.95.2 and the current libc from CVS.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labs completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg