public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zaniyah at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/29183] cc1: internal compiler error: Segmentation Fault
Date: Tue, 26 Sep 2006 12:53:00 -0000	[thread overview]
Message-ID: <20060926125337.19199.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29183-13289@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from zaniyah at gmail dot com  2006-09-26 12:53 -------
Subject: Re:  cc1: internal compiler error: Segmentation Fault

Thanks, I have since spoken to our techies and discovered that this is
a wierd custom build that has just been left floating around on our
servers and somehow ended up on my path (it's great being the new
guy).

Thanks for looking into it.  Sorry to waste your time.

Jess

On 23 Sep 2006 10:05:47 -0000, rguenth at gcc dot gnu dot org
<gcc-bugzilla@gcc.gnu.org> wrote:
>
>
> ------- Comment #2 from rguenth at gcc dot gnu dot org  2006-09-23 10:05 -------
> gcc -g -Wall -D -I . -I ../Common/MemMgmt  -I ../Common/StringMgmt -I
>
> The '-D -I .' part is broken.  Remove the -D.
>
> Otherwise we cannot do anything about bugs without a testcase.
>
>
> --
>
> rguenth at gcc dot gnu dot org changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |RESOLVED
>          Resolution|                            |INVALID
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29183
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29183


      parent reply	other threads:[~2006-09-26 12:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-22 14:53 [Bug c/29183] New: " zaniyah at gmail dot com
2006-09-22 16:08 ` [Bug c/29183] " pinskia at gcc dot gnu dot org
2006-09-23 10:05 ` rguenth at gcc dot gnu dot org
2006-09-26 12:53 ` zaniyah at gmail dot com [this message]

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=20060926125337.19199.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).