From: Paolo Ornati <ornati@fastwebnet.it>
To: Paolo Ornati <ornati@fastwebnet.it>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Random GCC segfaults -- Was: [2.6.16] slab error in slab_destroy_objs(): cache `radix_tree_node'...
Date: Tue, 28 Mar 2006 09:55:21 +0200 [thread overview]
Message-ID: <20060328095521.52ea3424@localhost> (raw)
In-Reply-To: <20060326215346.1b303010@localhost>
On Sun, 26 Mar 2006 21:53:46 +0200
Paolo Ornati <ornati@fastwebnet.it> wrote:
> PS: I've got another "gcc segfault" trying to build Qt again after a
> reboot but I don't think this is a memory problem (actually I have
> a memory problem (single bit error) but it should be cured with
> memmap=1K$214014K ;).
I've got others NON reproducible gcc segfaults, usually compiling some
huge CPP source.
Now I'm back to 2.6.15.6 and I'm stress testing GCC, no segfaults so
far.
Doing a git-bisect is maybe possible... but it will take ages since I
don't have a test case :(!
Additionally there's the slab error (seen just one time)...
If anyone have some idea like try-to-revert-this-patch let me know.
--
Paolo Ornati
Linux 2.6.15.6 on x86_64
next prev parent reply other threads:[~2006-03-28 7:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 19:53 [2.6.16] slab error in slab_destroy_objs(): cache `radix_tree_node' Paolo Ornati
2006-03-28 7:55 ` Paolo Ornati [this message]
2006-03-28 8:41 ` Random GCC segfaults -- Was: " Andrew Morton
2006-03-28 9:22 ` Paolo Ornati
2006-03-28 11:48 ` Paolo Ornati
2006-03-28 13:23 ` Pavel Machek
2006-03-28 14:30 ` Paolo Ornati
2006-03-28 14:38 ` Paolo Ornati
2006-03-31 14:55 ` Random GCC segfaults --> Just Bad Memory Paolo Ornati
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=20060328095521.52ea3424@localhost \
--to=ornati@fastwebnet.it \
--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