public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jason Borden <jborden@sorenson.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: c/7502: internal error: Segmentation fault
Date: Mon, 05 Aug 2002 22:56:00 -0000	[thread overview]
Message-ID: <20020806055600.2084.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/7502; it has been noted by GNATS.

From: Jason Borden <jborden@sorenson.com>
To: "'gcc-gnats@gcc.gnu.org '" <gcc-gnats@gcc.gnu.org>
Cc:  
Subject: RE: c/7502: internal error: Segmentation fault
Date: Mon, 5 Aug 2002 23:47:35 -0600 

 This bug can be closed. Come to find out, the problem was caused by one of
 the last things that I thought it would be. I upgraded the bios on my
 motherboard and all of the sudden, no more internal error: Segmentation
 fault . Chalk this one up as one of the weirdest problems I've encountered.
 Thanks, Jason
 
 -----Original Message-----
 From: gcc-gnats@gcc.gnu.org
 To: Jason Borden
 Sent: 8/5/02 5:26 PM
 Subject: Re: c/7502: internal error: Segmentation fault
 
 Thank you very much for your problem report.
 It has the internal identification `c/7502'.
 The individual assigned to look at your
 report is: unassigned. 
 
 >Category:       c
 >Responsible:    unassigned
 >Synopsis:       internal error: Segmentation fault
 >Arrival-Date:   Mon Aug 05 16:26:01 PDT 2002


             reply	other threads:[~2002-08-06  5:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-05 22:56 Jason Borden [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-25  4:01 paolo
2002-08-05 16:26 Jason Borden

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=20020806055600.2084.qmail@sources.redhat.com \
    --to=jborden@sorenson.com \
    --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: 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 read-only IMAP folder(s) and NNTP newsgroup(s).