public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Jeandel <ejeandel@ens-lyon.fr>
To: linux-msdos@vger.kernel.org
Subject: Re: segfault with backtrace and information
Date: Sat, 14 Dec 2002 14:23:22 +0100	[thread overview]
Message-ID: <20021214132322.GA32460@ens-lyon.fr> (raw)
In-Reply-To: <20021208203022.GA5036@dirac.org>

Peter Jay Salzman said :
> dosemu consistantly segfaults on one of my machines.
> 
> 
> the area of code:
> 
>    (gdb) l 707
>    702     {STRQUOTELESS}          MAY_BEFORME {
>    703                               yylval->s_value = strdup(yytext);
>    704                               EXPRTYPE(yylval->s_value) = TYPE_STRQUOTELESS;
>    705                               return(STRING); }
> [snip]
Hi,

I encounter the same bug using gcc 3.2.2, bison 1.75 and flex 2.5.4

I found that parser.c calls yylex without arguments, whereas lex.yy.c defines 
yylex to be of type yylex(YYTYPE *yylval).

That means that bison does not build a pure parser, although YYPURE 
was defined.

I do not know exactly whether it is gcc or bison that is behaving wrong,
but inserting the line : 

%pure-parser

in the file parser.y.in (after the line: %start lines, for example)
was sufficient for me to solve this problem.

Regards,
Emmanuel

  parent reply	other threads:[~2002-12-14 13:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-08 20:30 segfault with backtrace and information Peter Jay Salzman
2002-12-08 20:31 ` Peter Jay Salzman
2002-12-14 13:23 ` Emmanuel Jeandel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-09 17:34 Stas Sergeev

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=20021214132322.GA32460@ens-lyon.fr \
    --to=ejeandel@ens-lyon.fr \
    --cc=E_Jeandel@mail.dotcom.fr \
    --cc=linux-msdos@vger.kernel.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