lkcd
[Top] [All Lists]

Re: Msg: input buffer overflow in lcrash.

To: "Matt D. Robinson" <yakker@xxxxxxxxxxxxxx>
Subject: Re: Msg: input buffer overflow in lcrash.
From: Luc Chouinard <lucc@xxxxxxx>
Date: Tue, 31 Jul 2001 14:39:56 -0400
Cc: Evandro Tadeu S Vargas <gevandro@xxxxxxxxxx>, lkcd@xxxxxxxxxxx
Organization: SGI
References: <OF03258DED.8AAA17E8-ON83256A9A.0055A971@LocalDomain> <3B66F092.98D5D11F@xxxxxxxxxxxxxx>
Sender: owner-lkcd@xxxxxxxxxxx
"Matt D. Robinson" wrote:
> 
> Evandro Tadeu S Vargas wrote:
> >
> > Hi,
> >
> >      I'm  testing lcrash in Linux/390 (Suse 2.2.16) for processing dump.
> > After compiler the lkcdutils,
> >  i created an dump (using Linux/390 standalone dump) and lcrash show
> > following msg:
> >
> >               input buffer overflow, can't enlarge buffer because scanner
> > uses REJECT
> >
> >      Could you explain this message and possible solution ?
> >
> >                  TIA.
> >                                              Evandro Vargas
> 
> I'm not precisely sure as of yet, but it looks like this is generated
> by flex (out of libsial), not anything 'lcrash' is doing.  The problem
> is that YY_USES_REJECT is being defined (no REJECTs in the flex code),
> so you can try to build lex.sial.c and lex.sialpp.c with -UYY_USES_REJECT
> and see what results that gives you.
> 
> Just out of curiosity, how are you generating the message?  When you
> first try to start 'lcrash'?  And if so, what does your command line
> look like?
> 
> Thanks ...
> 
> --Matt
> 
> P.S.  I don't have an S/390, so I can't test this.  Michael?

I started looking at this a bit earlier but I got side tracked in doing
something else. Matt is right about the YY_USES_REJECT define and the -U
workaround should get you out of trouble. The question I still need to
answer is why, with your particular configuration, YY_USES_REJECT is
being defined. It's is not being defined on my RH60 build.

I think I see a link beeween the -l option (lex compatibility) and
YY_USES_REJECT being defined, but without a more scrutinized look I'm
not sure if it's the only condition that can do this.

-- 
Luc

<Prev in Thread] Current Thread [Next in Thread>