FLEX, was Re: Return value of malloc(0)

Peter Jeremy peterjeremy at optushome.com.au
Fri Jun 30 08:10:26 UTC 2006

On Thu, 2006-Jun-29 15:09:23 -0700, Randall Hyde wrote:
>>How about feeding the C source through the preprocessor, stripping out
>>the #line directives, compiling it and posting the exact gcc error and
>>source context.
>Okay, I'll try that when I get home. But I was kind of under the
>impression that *GCC* runs the preprocessor on the input, during
>compilation :-).

It does but, as you pointed out, the input line you posted doesn't
obviously correlate with the error report.  Explicitly pre-processing
the source and stripping out the #line directives means that you can
then correlate the error message with the actual line that cc1 is

> -- this would appear to be a generic problem with using FLEX
>output under BSD and I thought a quick question would affirm/deny
>that thought.

Well, I just did a check of some flex code I have lying around and it
did not report any syntax errors or unexpected warnings.  And, since
flex is used several times during a buildworld, any generic problems
would show up very quickly.

Peter Jeremy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20060630/9275c8ac/attachment.pgp

More information about the freebsd-hackers mailing list