This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: fixproto crash
- To: law at cygnus dot com
- Subject: Re: fixproto crash
- From: Zack Weinberg <zack at rabi dot columbia dot edu>
- Date: Fri, 18 Dec 1998 00:59:24 -0500
- cc: egcs at cygnus dot com
On Thu, 17 Dec 1998 22:38:54 -0700, Jeffrey A Law wrote:
>
> In message <199812152218.OAA23750@adsl-206-170-148-33.dsl.pacbell.net>you wr
>i
>te:
> > fixproto: populating `include'
> > ../../gcc/fixproto[251]: 277590 Bus error(coredump)
> >
> > While I understand that `various warnings and error messages from
> > fixproto are normal', I would not expect `coredump' to be among them.
>Yup.
>
> > Interestingly, the build continues; only my eagle eyes :-) spotted
> > this possible problem.
>Yea, this probably explains why I didn't "see" the problem recently -- now
>to find that patch which was supposed to fix this bug.
Would this be the #include_next in primary source file bug, which I
believe Dave B and I squashed?
1998-12-16 Zack Weinberg <zack@rabi.phys.columbia.edu>
* cpplib.c (do_include): Treat #include_next in the
primary source file as #include plus warning. Treat
#include_next in a file included by absolute path as an
error. fp == CPP_NULL_BUFFER is a fatal inconsistency.
Unfortunately I don't have access to the platform in question (hpux,
right?) so can't confirm this.
zw