Re: [ng-spice-devel] Re: [ng-spice] fix for segfaults


To ng-spice-devel@ieee.ing.uniroma1.it
From Daniel Bertrand <d.bertrand@ieee.org>
Date Fri, 28 Sep 2001 20:39:51 -0700 (PDT)
Delivered-To mailing list ng-spice-devel@ieee.ing.uniroma1.it
In-reply-to <Pine.LNX.3.96.1010928222855.379A-100000@wep08-1.wep.tudelft.nl >
Mailing-List contact ng-spice-devel-help@ieee.ing.uniroma1.it; run by ezmlm
Reply-To ng-spice-devel@ieee.ing.uniroma1.it

On Fri, 28 Sep 2001, Bas Gieltjes wrote:

> I have access to two Linux machines where I tried to compile
> ng-spice-rework-14pre3.tgz, one machine has more processor power and
> memory which is useful for compilation with debugging information.
>
> Both machines compiled the ngspice source where one machine has the patch
> above, both compiled ngspice versions gave a segfault. I have compiled one
> ngspice with debug information and tried if gdb would give me useful
> information, I am not familiar with gdb and the information given was
> useless to me. I need to look for more information about gdb so i am able
> to use it better. I have the gdb output scribbled on a piece of paper and
> it says this:
> program received signal SIGSEGV; segmentation fault.
> 0x40482109 in_strol_internal() from /lib/libc.so.6
> It might be useful for someone else.

Hi,

I'm experiencing the same problem, I think it's a problem with the i686
version of glibc (with 2.2.4 under Redhat, at least). I downgraded to the
i386 version and the problem seems to have gone away (unfortunately, other
apps (mozilla) seem to have broken...).

I also don't have this problem at all on an old pentium 133 box (running
RH7.1, glibc-2.2.2-i386).



-- 
Daniel Bertrand






Partial thread listing: