#1134: Extremely weird stack trace produced my Parrot when allocating things in
a
long loop in Rakudo
-------------------+--------------------------------------------------------
Reporter: masak | Type: bug
Status: new | Priority: normal
Milestone: | Component: GC
Version: 1.7.0 | Severity: high
Keywords: | Lang:
Patch: | Platform:
-------------------+--------------------------------------------------------
Comment(by whiteknight):
I've seen this same backtrace a few days ago, and it's extremely strange.
Some points:
- Parrot_str_from_int does not call Parrot_NameSpace_get_isa
- new_runloop_jump_point() does not call itself, and does not call into
the runcore.
- pmc_new() does not call pmc_reuse().
- Parrot_gc_is_blocked_GC_sweep() is a simple accessor. It doesn't call
itself recursively and doesn't call Parrot_gc_mark_PObj_alive
...And the list goes on and on. In short, this backtrace is nonsensical in
every possible way.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1134#comment:1>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
