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

2006-06-30 Thread Peter Jeremy
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

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

2006-06-29 Thread Randall Hyde
-Original Message- >From: Thomas David Rivers <[EMAIL PROTECTED]> >Sent: Jun 29, 2006 3:17 AM >To: freebsd-hackers@freebsd.org, [EMAIL PROTECTED] >Subject: Re: FLEX, was Re: Return value of malloc(0) > >"Randall Hyde" <[EMAIL PROTECTED]> >&g

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

2006-06-29 Thread Randall Hyde
-Original Message- > >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 preproces

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

2006-06-29 Thread Thomas David Rivers
"Randall Hyde" <[EMAIL PROTECTED]> > > BTW, if anyone is intrested in the full FLEX source, it's part of the HLA > (High Level Assembler) source package found here: > > > http://webster.cs.ucr.edu/AsmTools/HLA/HLAv1.84/hlasrc.zip > Just wondering if those guys knew that IBM calls their mainfra

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

2006-06-28 Thread Peter Jeremy
On Wed, 2006-Jun-28 22:40:45 -0700, Randall Hyde wrote: >I seriously doubt seeing the code will do much good. >Here's the offending line: > > YY_INPUT( (&yy_current_buffer->yy_ch_buf[number_to_move]), > yy_n_chars, num_to_read ); How about feeding the C source through the preprocessor, strippi

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

2006-06-28 Thread Steve Kargl
On Wed, Jun 28, 2006 at 10:40:45PM -0700, Randall Hyde wrote: > > > > > > > Without seeing the code or the actual error message, I'm > > guessing the answer is 42. Perhaps, some detail might > > be appropriate. > > I seriously doubt seeing the code will do much good. > Here's the offending line:

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

2006-06-28 Thread Randall Hyde
> > > > Without seeing the code or the actual error message, I'm > guessing the answer is 42. Perhaps, some detail might > be appropriate. I seriously doubt seeing the code will do much good. Here's the offending line: YY_INPUT( (&yy_current_buffer->yy_ch_buf[number_to_move]), yy_n_chars,