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

Regex match can cause Null PMC access (in a given / if) #946

Closed
p6rt opened this issue Apr 24, 2009 · 6 comments
Closed

Regex match can cause Null PMC access (in a given / if) #946

p6rt opened this issue Apr 24, 2009 · 6 comments

Comments

@p6rt
Copy link

p6rt commented Apr 24, 2009

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

Searchable as RT65080$

@p6rt
Copy link
Author

p6rt commented Apr 24, 2009

From @moritz

08​:57 <@​moritz_> rakudo​: given 'foo' { if /bar/ { 1 } }
08​:57 < p6eval> rakudo 9a5305​: OUTPUT«Null PMC access in isa_pmc()␤current
  instr.​: 'parrot;PGE;Match;new' pc 33
  (compilers/pge/PGE/Match.pir​:64)␤»

Funnily when I add a line like this​:

lives_ok { given 'foo' { if /bar/ { 1 } } }, 'blubb';

to an existing spectest it passes, so I guess it's something rather
weird, and I don't even know how to test it (until we get qx, of course).

Cheers,
Moritz

@p6rt
Copy link
Author

p6rt commented Aug 13, 2009

From @kyleha

On Fri Apr 24 00​:09​:43 2009, moritz wrote​:

08​:57 <@​moritz_> rakudo​: given 'foo' { if /bar/ { 1 } }
08​:57 < p6eval> rakudo 9a5305​: OUTPUT«Null PMC access in isa_pmc()␤current

I tried today's Rakudo, and this doesn't happen anymore. I haven't
added a test for this since, as noted, it defies testing. I guess this
ticket will be open for eternity. 8-)

@p6rt
Copy link
Author

p6rt commented Aug 13, 2009

@kyleha - Status changed from 'new' to 'open'

@p6rt
Copy link
Author

p6rt commented Aug 13, 2009

From @kyleha

I went back to the Rakudo that had this problem and recreated it. It
seems this only happens when the code in question is at the end of
input. If anything is after it, it's fine. I tried putting it in an
eval to simulate "end of file", but that did not exhibit the problem.

I tried running with parrot -G, and that didn't make a difference.

@p6rt
Copy link
Author

p6rt commented Mar 9, 2010

From @moritz

The problem is gone; I'll close without a test.

@p6rt
Copy link
Author

p6rt commented Mar 9, 2010

@moritz - Status changed from 'open' to 'resolved'

@p6rt p6rt closed this as completed Mar 9, 2010
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