This is the mail archive of the mailing list for the glibc project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Crash during build on UltraSPARC, 32-bit glibc

On Sat, Nov 08, 2003 at 08:12:39PM +0000, Nix wrote:
> On Sat, 8 Nov 2003, Carlos O'Donell spake:
> > On Wed, Oct 22, 2003 at 06:47:16AM +0100, Nix wrote:
> >> I reported the crash here because it happens without Debian's patches
> >> too (with a completely unpatched toolchain). So it can't be their fault.
> > 
> > Have you looked at the configure options that debian uses for sparc?
> > Perhaps your options are *not* safe to use.
> I've turned off my site-config file, so the default CFLAGS are in
> use. Debian has no special CFLAGS for sparc32 that I can see; it rams
> -O2 in for everything.
> (As for configure options, debian/rules and debian/sysdeps/* don't show
> any particularly shocking ones. I've tried forcing BUILD_CFLAGS of -O2
> as Debian do: no change. Likewise if I use --disable-omitfp (not that
> -fomit-frame-pointer does much on sparc).
> I'll have to look through the Debian GCC and binutils patches again, I
> think: I might have to resort to installing a minimal Debian development
> installation and trying a build in there (although that feels like
> giving up: I won't learn anything that way).

The thing to do at this stage is what everyone does. Start debugging
the dynamic loader and see where it dies. Is it inside a library import
stub? Is it inside a library? During init? Is the PIC register corrupt,
is the stack corrupt? You need to be intimately familiar with sparc in
order to fix some of these types of problems.

It's hard to learn if your in over your head.


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