public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Samium Gromoff" <_deepfire@mail.ru>
To: linux-kernel@vger.kernel.org
Subject: strange gcc crashes...
Date: Sat, 11 Aug 2001 18:58:17 +0400	[thread overview]
Message-ID: <E15VaDR-000N0H-00@f9.mail.ru> (raw)

       I`ve experienced strange gcc sig11 crashes.
    prerequisities: gcc-2.95.3-vanille, 2.4.7-vanille

    recently i`ve dloaded arachne, a svgalib-based
    web browser. It has quite a number of various problems,
    with console-switching screen/terminal corruptions
    being most significant. so as i said, it crashed
    alot, and i recovered from these crashes w/o reboot.

    then i get libggi-2.0.4b4. (that is all happening
    w/o reboot between actions)

    i`ve started compile process. bah! - sig11.

    Although i quite often have those, but
    this time i had about _100_ of them!!!
    all these in libggi. I `ve got tired of tweakin` 
    cflags of different makfiles, because it helps
    to go thru prblematic .c`s, and i rebooted.

    Hm the /most/ mystic of all this is the fact, that 
    after reboot sig11 rate dropped from sig11 per ~4
    files to one per ~120 of them. To make clear
    the situation, i`ll tell that libggi is VERY
    broken for me in the scope of gcc`s sig11.

    also i can say, that the sig11/file rate had been
    constantly increasing with the compilation process.

    so it seems to me like kernel problem...

    further information upon request.

---


cheers,


   Samium Gromoff

             reply	other threads:[~2001-08-11 14:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-11 14:58 Samium Gromoff [this message]
2001-08-11 15:16 ` strange gcc crashes Ignacio Vazquez-Abrams
2001-08-11 18:38   ` Horst von Brand
2001-08-11 16:42 ` J.H.M. Dassen (Ray)
  -- strict thread matches above, loose matches on Subject: below --
2001-08-13 11:55 Samium Gromoff
2001-08-13 12:04 ` Rasmus Andersen
2001-08-13 12:56 ` Nicholas Knight
2001-08-13 19:26   ` Josh McKinney

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=E15VaDR-000N0H-00@f9.mail.ru \
    --to=_deepfire@mail.ru \
    --cc=linux-kernel@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