[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: DDD 3.3.1 (i586-mandrake-linux-gnu) gets `Segmentation fault' signal
From: |
J.H.M. Dassen (Ray) |
Subject: |
Re: DDD 3.3.1 (i586-mandrake-linux-gnu) gets `Segmentation fault' signal |
Date: |
Mon, 15 Jul 2002 22:44:32 +0200 |
User-agent: |
Mutt/1.4i |
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?
- Does switching to gcc 3.1-compiled versions of all libraries DDD uses
(including X, ncurses and glibc) make a difference?
- Can you reproduce the problem when using DDD CVS (which is what Debian is
actually using at the moment)?
- Is the problem reproducable with a plain glibc build for x86, not
optimised for i686?
HTH,
Ray
--
RUMOUR Believe all you hear. Your world may not be a better one than the one
the blocks live in but it'll be a sight more vivid.
- The Hipcrime Vocab by Chad C. Mulligan