texmacs-dev
[Top][All Lists]
Advanced

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

Re: [Texmacs-dev] Segmentation fault with gcc 3.2


From: Igor V. Kovalenko
Subject: Re: [Texmacs-dev] Segmentation fault with gcc 3.2
Date: Thu, 31 Oct 2002 00:14:47 +0300
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020809

Joris van der Hoeven wrote:
Hi *,

I now tried to compile both TeXmacs and Guile with gcc 3.2.

I recall that gcc was compiled using gcc 2.95.3 and
that I *only* recompiled the GNU compiler collection
(so no other libraries have been recompiled using gcc 3.2).

Again, the result works without problems; no segmentation faults...

<Joris>


So... we are now at the checkpoint, telling the truth :)
Mine is as follows:

----------------------------------------------------------------------------

$ ldd /usr/libexec/TeXmacs-1.0.0.20/bin/texmacs.bin
        libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x40025000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40033000)
        libguile.so.9 => /usr/lib/libguile.so.9 (0x40111000)
        libm.so.6 => /lib/i686/libm.so.6 (0x40184000)
        libdl.so.2 => /lib/libdl.so.2 (0x401a6000)
        libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x401aa000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x4025e000)
        libc.so.6 => /lib/i686/libc.so.6 (0x42000000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

----------------------------------------------------------------------------

$ strings -a /usr/lib/libguile.so.9.0.0 |grep GCC|sort|uniq
GCC: (GNU) 3.2 20021021 (Red Hat Linux 8.0 3.2-11)
[so this is a pure recompile with installed GCC]

----------------------------------------------------------------------------

$ strings -a /usr/libexec/TeXmacs-1.0.0.20/bin/texmacs.bin | grep GCC|sort|uniq
GCC: (GNU) 3.2 20021021 (Red Hat Linux 8.0 3.2-11)
[so this is a pure recompile with installed GCC]

----------------------------------------------------------------------------

$ strings -a /lib/libgcc_s.so.1 |grep GCC|sort|uniq
GCC_3.0
GCC: (GNU) 3.2 20020903 (Red Hat Linux 8.0 3.2-7)
GCC: (GNU) 3.2 20021021 (Red Hat Linux 8.0 3.2-11)
[so this is a mixed GCC compilation]

----------------------------------------------------------------------------

$ strings -a /usr/lib/libstdc++.so.5|grep GCC|sort|uniq
GCC_3.0
GCC: (GNU) 3.2 20020903 (Red Hat Linux 8.0 3.2-7)
GCC: (GNU) 3.2 20021021 (Red Hat Linux 8.0 3.2-11)
_Unwind_DeleteException@@GCC_3.0
_Unwind_GetDataRelBase@@GCC_3.0
_Unwind_GetIP@@GCC_3.0
_Unwind_GetLanguageSpecificData@@GCC_3.0
_Unwind_GetRegionStart@@GCC_3.0
_Unwind_GetTextRelBase@@GCC_3.0
_Unwind_RaiseException@@GCC_3.0
_Unwind_Resume@@GCC_3.0
_Unwind_SetGR@@GCC_3.0
_Unwind_SetIP@@GCC_3.0
[so this is a mixed GCC compilation]

----------------------------------------------------------------------------

Related packages are:

gcc-c++-3.2-11
gcc-g77-3.2-11
libgcc-3.2-11
gcc-3.2-11
binutils-2.13.90.0.10-3
libstdc++-3.2-11
compat-libstdc++-7.3-2.96.110
libstdc++-devel-3.2-11
glibc-common-2.3.1-5
glibc-kernheaders-2.4-8.1.1
glibc-utils-2.3.1-5
glibc-devel-2.3.1-5
glibc-2.3.1-5

----------------------------------------------------------------------------

guile-1.4-8 custom rebuild from guile-1.4-8.src.rpm with

./configure  --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu 
--target=i386-redhat-linux-gnu \
    --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin 
--sbindir=/usr/sbin \
    --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include 
--libdir=/usr/lib \
    --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com \
    --mandir=/usr/share/man --infodir=/usr/share/info --without-threads 
--enable-ltdl-convenience

[straight from config.status, the only modification of mine was disabling 
threads]

----------------------------------------------------------------------------

Comments?

GCC is the suspect, and it's libstdc++ implementation too.
Also guile may be the cause. I looked at the internals, they are doing
much of pointer magic to do guile things, and current GCC may not like this
(aliasing stuff, I freely speculate here). Also there are more subtle problems
introduced/uncovered by current GCC...

--
Regards,
Igor V. Kovalenko    mailto: iko at crec dot mipt dot ru





reply via email to

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