public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sugioka at itonet dot co dot jp" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/26936]  New: fix-header segfault with glibc-2.4 header
Date: Thu, 30 Mar 2006 07:49:00 -0000	[thread overview]
Message-ID: <bug-26936-8402@http.gcc.gnu.org/bugzilla/> (raw)

On bootstrapping, fix-header segfaults while processing
/usr/include/bits/stdio-ldbl.h which is from glibc-2.4.

This problem does not appear on i386-linux host because 'use_fixproto' is set
to 'no' in gcc/config.gcc.

Reduced problematic header contents:
f()

Reproduce:
    cd <build-dir>/gcc
    make stmp-fixproto
    cd build
    echo 'f()' >f.h
    ./fix-header bits/f.h f.h bits/f.h
  Segmentation fault


-- 
           Summary: fix-header segfault with glibc-2.4 header
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: sugioka at itonet dot co dot jp
  GCC host triplet: sh4-unknown-linux


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


             reply	other threads:[~2006-03-30  7:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-30  7:49 sugioka at itonet dot co dot jp [this message]
2006-03-30  9:45 ` [Bug bootstrap/26936] " rguenth at gcc dot gnu dot org
2006-03-30 11:50 ` sugioka at itonet dot co dot jp
2006-03-31  7:50 ` rguenth at gcc dot gnu dot org
2006-03-31  7:50 ` rguenth at gcc dot gnu dot org
2006-03-31 21:44 ` pinskia at gcc dot gnu dot org

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=bug-26936-8402@http.gcc.gnu.org/bugzilla/ \
    --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).