[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

build segfault with 2.3.1

From: Maciej Babinski
Subject: build segfault with 2.3.1
Date: Wed, 29 Jan 2003 16:15:24 -0600
User-agent: Mutt/1.4i

Hi, I'm having a a problem getting 2.3.1 to build on my x86 linux
system. My CPU is a PentiumMMX 200. The build fails as follows:

make  -C sunrpc others
make[1]: Entering directory `/usr/src/glibc-2.3.1/sunrpc'
CPP='/usr/opt/packages/gcc-3.2.1/bin/gcc -E -x c-header'  ../elf/ld-linux.so.2 
 ./rpcgen -Y ../scripts -c rpcsvc/bootparam_prot.x -o xbootparam_prot.T
make[1]: *** [xbootparam_prot.stmp] Segmentation fault
make[1]: Leaving directory `/usr/src/glibc-2.3.1/sunrpc'
make: *** [sunrpc/others] Error 2

If I run this command through gdb, I get the following:
(gdb) run
Starting program: /usr/src/glibc-2.3.1/elf/ld.so --library-path 
 ./rpcgen -Y ../scripts -c rpcsvc/bootparam_prot.x -o xbootparam_prot.T

Program received signal SIGSEGV, Segmentation fault.
0x8000d13f in _itoa ()
(gdb) bt
#0  0x8000d13f in _itoa ()
#1  0x8000aa76 in _dl_debug_vdprintf ()
#2  0x8000ac48 in _dl_dprintf ()
#3  0x8000cf01 in __assert_fail ()
#4  0x80001047 in _dl_start ()

Running any other binaries with the built version of ld-linux.so
yields a segfault at the same address with the same backgrace.
I can reproduce the problem with binutils 2.13 and 2.13.2, as well
as gcc 3.2 and 3.2.1. I tracked down a similar bug report in the gcc
mailing list, however it pertained to an unreleased CVS build of gcc,
and involved a call to a NULL function pointer, whereas in my problem,
the code at the address of the fault is:
        0x8000d13f <_itoa+79>:  mov    (%eax,%edx,1),%al

and the assembly that follows doesn't appear to have anything to do
with a function call.

I'd appreciate a pointer to where to look next, or any information
you can give me on what the problem could be.  Let me know if you
need any more information. I can provide a disassembled dump of
the function if necessary. Thank you.

                                           Maciej Babinski

reply via email to

[Prev in Thread] Current Thread [Next in Thread]