Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assertion failure in perl_yylex (toke.c:6333) #16303

Closed
p5pRT opened this issue Dec 15, 2017 · 7 comments
Closed

Assertion failure in perl_yylex (toke.c:6333) #16303

p5pRT opened this issue Dec 15, 2017 · 7 comments

Comments

@p5pRT
Copy link

p5pRT commented Dec 15, 2017

Migrated from rt.perl.org#132583 (status was 'resolved')

Searchable as RT132583$

@p5pRT
Copy link
Author

p5pRT commented Dec 15, 2017

From @geeknik

This assertion failure was triggered in Perl v5.27.6-156-g5d4548b73b,
compiled with Clang 6.0.0-trunk and -fsanitize=address.

./perl -e 'format=
^
0m}}
.'

perl​: toke.c​:6333​: int Perl_yylex(void)​: Assertion
`((char*)PL_scopestack_name[PL_scopestack_ix-1] == (char*)"lex_format") ||
strEQ(PL_scopestack_name[PL_scopestack_ix-1], "lex_format")' failed.
Aborted

#0 __GI_raise (sig=sig@​entry=6) at ../sysdeps/unix/sysv/linux/raise.c​:58
#1 0x00007ffff6cc837a in __GI_abort () at abort.c​:89
#2 0x00007ffff6cbeb47 in __assert_fail_base (fmt=<optimized out>,
assertion=assertion@​entry=0xc555c0 <.str.182>
"((char*)PL_scopestack_name[PL_scopestack_ix-1] == (char*)\"lex_format\")
|| strEQ(PL_scopestack_name[PL_scopestack_ix-1], \"lex_format\")",
file=file@​entry=0xc4b240 <.str.1> "toke.c",
  line=line@​entry=6333, function=function@​entry=0xc4d840
<__PRETTY_FUNCTION__.Perl_yylex> "int Perl_yylex(void)") at assert.c​:92
#3 0x00007ffff6cbebf2 in __GI___assert_fail (assertion=0xc555c0 <.str.182>
"((char*)PL_scopestack_name[PL_scopestack_ix-1] == (char*)\"lex_format\")
|| strEQ(PL_scopestack_name[PL_scopestack_ix-1], \"lex_format\")",
file=0xc4b240 <.str.1> "toke.c", line=6333,
  function=0xc4d840 <__PRETTY_FUNCTION__.Perl_yylex> "int
Perl_yylex(void)") at assert.c​:101
#4 0x000000000064d2ec in Perl_yylex () at toke.c​:6333
#5 0x00000000006a67f4 in Perl_yyparse (gramtype=<optimized out>) at
perly.c​:340
#6 0x00000000005a3c22 in S_parse_body (env=<optimized out>,
xsinit=<optimized out>) at perl.c​:2447
#7 0x000000000059ea24 in perl_parse (my_perl=<optimized out>,
xsinit=0x5036f0 <xs_init>, argc=2, argv=<optimized out>, env=0x0) at
perl.c​:1750
#8 0x0000000000503486 in main (argc=0, argv=0x7ffff6cc677f
<__GI_raise+159>, env=0x7fffffffe380) at perlmain.c​:121

@p5pRT
Copy link
Author

p5pRT commented Jan 21, 2019

From @tonycoz

On Thu, 14 Dec 2017 20​:46​:01 -0800, brian.carpenter@​gmail.com wrote​:

This assertion failure was triggered in Perl v5.27.6-156-g5d4548b73b,
compiled with Clang 6.0.0-trunk and -fsanitize=address.

./perl -e 'format=
^
0m}}
.'

This looks like it was fixed by 8174801.

Tony

@p5pRT
Copy link
Author

p5pRT commented Jan 21, 2019

The RT System itself - Status changed from 'new' to 'open'

@p5pRT
Copy link
Author

p5pRT commented Jan 23, 2019

From @tonycoz

On Sun, 20 Jan 2019 19​:26​:47 -0800, tonyc wrote​:

On Thu, 14 Dec 2017 20​:46​:01 -0800, brian.carpenter@​gmail.com wrote​:

This assertion failure was triggered in Perl v5.27.6-156-g5d4548b73b,
compiled with Clang 6.0.0-trunk and -fsanitize=address.

./perl -e 'format=
^
0m}}
.'

This looks like it was fixed by 8174801.

And closing.

Tony

@p5pRT
Copy link
Author

p5pRT commented Jan 23, 2019

@tonycoz - Status changed from 'open' to 'pending release'

@p5pRT
Copy link
Author

p5pRT commented May 22, 2019

From @khwilliamson

Thank you for filing this report. You have helped make Perl better.

With the release today of Perl 5.30.0, this and 160 other issues have been
resolved.

Perl 5.30.0 may be downloaded via​:
https://metacpan.org/release/XSAWYERX/perl-5.30.0

If you find that the problem persists, feel free to reopen this ticket.

@p5pRT
Copy link
Author

p5pRT commented May 22, 2019

@khwilliamson - Status changed from 'pending release' to 'resolved'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant