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

Seg fault declaring as both multi and non-multi #1248

Closed
p6rt opened this issue Aug 23, 2009 · 5 comments
Closed

Seg fault declaring as both multi and non-multi #1248

p6rt opened this issue Aug 23, 2009 · 5 comments
Labels

Comments

@p6rt
Copy link

p6rt commented Aug 23, 2009

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

Searchable as RT68748$

@p6rt
Copy link
Author

p6rt commented Aug 23, 2009

From @carbin

Happens with subs, methods and submethods. It depends on the order the
multi is declared (multi declared first or multi declared second is
the difference between no output and the segfault).

Just from my testing​:

sub foo {}; multi sub foo {};
Redefinition of routine foo
Segmentation fault

method foo {}; multi method foo {};
Segmentation fault

submethod foo {}; multi submethod foo {};
Segmentation fault

multi sub foo {}; sub foo {}; # doesn't die, no output

multi sub foo {}; sub foo {}; foo
Segmentation fault

multi sub foo {}; sub foo {}; foo; # with a semi-colon, doesn't die

multi method foo {}; method foo {};
Segmentation fault

multi submethod foo {}; submethod foo {}; # doesn't die, no output

multi submethod foo {}; submethod foo {}; foo
Segmentation fault

multi submethod foo {}; submethod foo {}; foo;
too few arguments passed (0) - 2 params expected
in submethod foo (<unknown>​:1)
called from Main (<unknown>​:1)

sub infix​:<> {}; multi sub infix​:<> {};
Redefinition of routine infix​:~
Segmentation fault

multi sub infix​:<> {}; sub infix​:<> {}; # doesn't die, no output

multi sub infix​:<> {}; sub infix​:<> {}; say "a"~"b";
Segmentation fault

Backtrace is at​: http://gist.github.com/173374

--
Carlin

@p6rt
Copy link
Author

p6rt commented Aug 24, 2009

From @bacek

On Sun Aug 23 11​:45​:53 2009, carlin wrote​:

Happens with subs, methods and submethods. It depends on the order the
multi is declared (multi declared first or multi declared second is
the difference between no output and the segfault).

Just from my testing​:

sub foo {}; multi sub foo {};
Redefinition of routine foo
Segmentation fault

Thanks a lot. parrot's segfault was fixed in r40750.

--
Bacek

@p6rt
Copy link
Author

p6rt commented Aug 24, 2009

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

@p6rt
Copy link
Author

p6rt commented Aug 3, 2010

From @bbkr

Those examples does not segfault on * release.

$ perl6 -v

This is Rakudo Perl 6, version 2010.07-47-g9fd5eaa built on parrot 2.6.0

Copyright 2008-2010, The Perl Foundation

Examples given in this ticket are similiar to test cases in multis
testsuite, no need to duplicate, so I'm just closing.

@p6rt
Copy link
Author

p6rt commented Aug 3, 2010

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

@p6rt p6rt closed this as completed Aug 3, 2010
@p6rt p6rt added the Bug label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant