Re: DDD 3.3.1 (i586-mandrake-linux-gnu) gets `Segmentation fault' signal

[Stew Benedict]

On Mon, 15 Jul 2002, J.H.M. Dassen (Ray) wrote:

> On Mon, Jul 15, 2002 at 15:12:51 -0400, Stew Benedict wrote:
> > What I was doing: Trying to run ddd.
> > 
> > We've moved to gcc-3.1.  lesstif and gdb have both been recompiled with
> > gcc-3.1.  I've tried relaxing compiler flags with no change.  Oddly enough
> > it runs on PPC with the same compiler/libs.
> 
> Hmm... in Debian, we've been using gcc 3.1 as the primary compiler on
> several non-x86 architectures for some time now; I haven't had any reports
> similar to the problem you're experiencing. Comparing your setup to
> Debian's, there are a few avenues to explore, in order of my decreasing
> "this could be it" gut feeling:
> - The backtrace looks like a memory allocation problem, quite possibly in
>   LessTif (Debian currently has a slightly older version of LessTif).
>   Do you get a different backtrace when attempting to run this DDD binary 
>   under Electric Fence?

[root@cooker root]# ef ddd

  Electric Fence 2.2.0 Copyright (C) 1987-1999 Bruce Perens
<bruce@perens.com>

ElectricFence Aborting: free(41418ff0): address not from malloc().

  Electric Fence 2.2.0 Copyright (C) 1987-1999 Bruce Perens
<bruce@perens.com>

warning: exec file is newer than core file.


Internal error (Illegal instruction).

Oops!  You have found a bug in DDD.

If you can reproduce this bug, please send a bug report
to <bug-ddd@gnu.org>, giving a subject like

    DDD 3.3.1 (i586-mandrake-linux-gnu) gets `Illegal instruction' signal

To enable us to fix the bug, you should include the following information:
* What you were doing to get this message.  Report all the facts.
* The contents of the `~/.ddd/log' file as generated by this session.
Please read also the section "Reporting Bugs" in the DDD manual.

We thank you for your support.


Internal error (Segmentation fault).

Oops!  You have found a bug in DDD.

If you can reproduce this bug, please send a bug report
to <bug-ddd@gnu.org>, giving a subject like

    DDD 3.3.1 (i586-mandrake-linux-gnu) gets `Segmentation fault' signal

To enable us to fix the bug, you should include the following information:
* What you were doing to get this message.  Report all the facts.
* The contents of the `~/.ddd/log' file as generated by this session.
Please read also the section "Reporting Bugs" in the DDD manual.

We thank you for your support.

/usr/bin/ef: line 20:  1614 Segmentation fault      (core dumped) ( export
LD_PRELOAD=libefence.so.0.0; exec $* )

Slightly different:

ef:

#0  0x405003c1 in kill () from /lib/i686/libc.so.6
#0  0x405003c1 in kill () from /lib/i686/libc.so.6
#1  0x400204ea in EF_Abort () from /usr/lib/libefence.so.0.0
#2  0x4001f73c in free () from /usr/lib/libefence.so.0.0
#3  0x40487353 in operator delete(void*) () from /usr/lib/libstdc++.so.4
#4  0x404873cf in operator delete[](void*) () from /usr/lib/libstdc++.so.4
#5  0x4042a608 in std::strstreambuf::~strstreambuf() ()
   from /usr/lib/libstdc++.so.4
#6  0x4042bfec in std::ostrstream::~ostrstream() ()
   from /usr/lib/libstdc++.so.4
#7  0x0807546b in strcpy ()
#8  0x08187db7 in glob_pattern_p ()
#9  0x081894a2 in glob_pattern_p ()
#10 0x080543b4 in strcpy ()
#11 0x404ef082 in __libc_start_main () from /lib/i686/libc.so.6
!  Segmentation fault

vs.

#0  0x405404d7 in malloc () from /lib/i686/libc.so.6
#0  0x405404d7 in malloc () from /lib/i686/libc.so.6
#1  0x40540312 in malloc () from /lib/i686/libc.so.6
#2  0x4032f81c in _XrmDefaultInitParseInfo () from
/usr/X11R6/lib/libX11.so.6
#3  0x40303e35 in _XrmInitParseInfo () from /usr/X11R6/lib/libX11.so.6
#4  0x402ee3ab in XrmGetFileDatabase () from /usr/X11R6/lib/libX11.so.6
#5  0x0818938d in glob_pattern_p ()
#6  0x080543b4 in strcpy ()
#7  0x404eb082 in __libc_start_main () from /lib/i686/libc.so.6

> - Does switching to gcc 3.1-compiled versions of all libraries DDD uses
>   (including X, ncurses and glibc) make a difference?

ncurses wasn't up to date on this machine, but it is now - same problem

> - Can you reproduce the problem when using DDD CVS (which is what Debian is
>   actually using at the moment)?

Yes - same (built without any rpm optimizations, just CVSMake, make)

Loaded symbols for /lib/libresolv.so.2
#0  0x405404d7 in malloc () from /lib/i686/libc.so.6
#0  0x405404d7 in malloc () from /lib/i686/libc.so.6
#1  0x40540312 in malloc () from /lib/i686/libc.so.6
#2  0x4032f81c in _XrmDefaultInitParseInfo () from
/usr/X11R6/lib/libX11.so.6
#3  0x40303e35 in _XrmInitParseInfo () from /usr/X11R6/lib/libX11.so.6
#4  0x402ee3ab in XrmGetFileDatabase () from /usr/X11R6/lib/libX11.so.6
#5  0x0815e42a in glob_pattern_p ()
#6  0x08052000 in strcpy ()
#7  0x404eb082 in __libc_start_main () from /lib/i686/libc.so.6
!  Segmentation fault

> - Is the problem reproducable with a plain glibc build for x86, not
>   optimised for i686?
> 

I dropped the:

%ifarch %{ix86}
#BuildFlags="-march=%{_target_cpu}"
BuildFlags=""
%endif

And did a clean glibc build/install.

And just to be sure, changed the symlinks of /lib/i686/libc.so.6 and
/lib/i686/libm.so.6 to point back to the generic /lib versions. Same
segfault.

Thx,
Stew Benedict

-- 
MandrakeSoft    
PPC FAQ: http://www.linux-mandrake.com/en/ppcFAQ.php3
IRC: irc.openproject.net #cooker-ppc