public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ahare@btinternet.com
To: gcc-gnats@gcc.gnu.org
Subject: other/4977: fix-header seg fault with recursive header files
Date: Fri, 23 Nov 2001 01:44:00 -0000 [thread overview]
Message-ID: <20011130230959.16510.qmail@sourceware.cygnus.com> (raw)
>Number: 4977
>Category: other
>Synopsis: fix-header seg fault with recursive header files
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Nov 30 15:16:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator: Andy Hare
>Release: Current CVS
>Organization:
>Environment:
Cygwin hosted cross compiling for arm-elf
>Description:
During building of a cross-compiler for the arm-elf using newlib, fix-header seg faults whilst working on dirent.h. Working through and getting fix-header to display the inlcuded files being opened shows that a recursive opening is happening. By stoping the recursive calling the problem goes away. scan_decls() function causes the problem where extern_C_braces_length gets longer than the array index it is being used as.
Disscussion on gcc-bugs mailing list under subject : Problems compiling current CVS under cygwin.
This gives more detail on the exact setup of the cross configure and build, as well as actual generated error messages.
>How-To-Repeat:
The following lines fails every time until the recursive dirent.h is removed.
/build/arm/gcc/gcc/fix-header dirent.h
/xgcc-arm/gnu/arm-elf/sys-include/dirent.h
/build/arm/gcc/gcc/include/dirent.h -D__STDC__=0 -D__cplusplus -I/build/arm/
gcc/gcc/include -I/xgcc-arm/gnu/arm-elf/sys-include
>Fix:
No fix, the work around is to remove the recursive header file. Ideally the fix-header program should fail with an error message indicating a recursive problem, not just crash.
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-11-30 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-23 1:44 ahare [this message]
2002-12-10 16:48 bangerth
2003-05-10 7:54 giovannibajo
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=20011130230959.16510.qmail@sourceware.cygnus.com \
--to=ahare@btinternet.com \
--cc=gcc-gnats@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).