public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: author@myrealbox.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: bootstrap/9592: Random Segfaults. System passed 2 torture tests. Date: Thu, 06 Feb 2003 15:14:00 -0000 [thread overview] Message-ID: <20030206151423.7800.qmail@sources.redhat.com> (raw) Synopsis: Random Segfaults. System passed 2 torture tests. State-Changed-From-To: open->feedback State-Changed-By: bangerth State-Changed-When: Thu Feb 6 15:14:23 2003 State-Changed-Why: How are we supposed to tackle the problem you describe? There are a number of people out there who build with such machines, and it does work for them. In order to fix bugs, we need a much better description of what you get, and how we can try to reproduce this. Please take a look at http://gcc.gnu.org/bugs.html for what we need. Just saying "My machine doesn't do what I think it should" is really not enough, sorry. Wolfgang http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9592
next reply other threads:[~2003-02-06 15:14 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-06 15:14 bangerth [this message] 2003-05-12 20:49 steven
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=20030206151423.7800.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=author@myrealbox.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).