linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kurt Kehler <kmk@pa.net>
To: linux-c-programming@vger.kernel.org
Subject: Re: Segmentation fault
Date: Tue, 16 Apr 2002 15:29:46 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.10204160238150.587-100000@darkstar.example.net> (raw)
In-Reply-To: <1328439575.20020411104849@kgpa.ru>

Oleg,

I'm adding this back in to the list.

On Thu, 11 Apr 2002, Oleg O. Ossovitskii wrote:

> Which hardware do You use? Which system do You use (kernel, glibc)?
> Does Your computer has FPU ? Try specify switch to gcc, that talk
> them use FPU emulate library. Unfortunately I don't remember which
> switch You should use.
> 
> I try use another compiler.
> 
> P.S. sorry for my poor english

My hardware is a 200mhz Pentium MMX running Slackware 4.0 with kernel
2.2.6.  dmesg reports "Intel Pentium with F0 0F bug - workaround
enabled."  I'm not sure that is relevant.  I tried several gcc
switches (-mno-486, -mno-fp-ret-in-387, -msoft-float) which didn't
work.  When I added the -O2 switch to gcc and ran a.out under gdb
I got:

Program received signal SIGSEGV, Segmentation fault.
0x40060607 in ldiv () from /lib/libc.so.5

What did work was booting Slackware 7.1 which uses egcs-2.91.66.
So there must be a problem with Slackware 4.0's libc5?  I realize
it is time to switch to more recent software.

Thanks Oleg,
Kurt Kehler


       reply	other threads:[~2002-04-16 19:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1328439575.20020411104849@kgpa.ru>
2002-04-16 19:29 ` Kurt Kehler [this message]
     [not found] <20020411084352.65e693fe.subscript@free.fr>
2002-04-16 19:30 ` Segmentation fault Kurt Kehler
     [not found] <OF5DFD5B6D.7D47A4C9-ON65256B98.0022D8F5@pune.tcs.co.in>
2002-04-16 19:30 ` Kurt Kehler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.10.10204160238150.587-100000@darkstar.example.net \
    --to=kmk@pa.net \
    --cc=linux-c-programming@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).