Fix receive op using wrong interp for write access to mailbox

VTABLE_shift_pmc is writing to the mailbox. This is ok, since it is protected by the mailbox_lock, but of course we have to do this with the partner's interp. Otherwise it would fail in the write barrier.
parrot · Apr 15, 2012 · c6e891e · c6e891e
1 parent 145ba94
commit c6e891e
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/src/ops/core_ops.c b/src/ops/core_ops.c
@@ -24275,7 +24275,7 @@ Parrot_receive_p(opcode_t *cur_opcode, PARROT_INTERP) {
         }
 
         if ((msg_count > 0)) {
-            PREG(1) = VTABLE_shift_pmc(interp, pdata->mailbox);
+            PREG(1) = VTABLE_shift_pmc(pdata->interp, pdata->mailbox);
             Parrot_unblock_GC_mark(interp);
             UNLOCK(pdata->mailbox_lock);
             {

diff --git a/src/ops/experimental.ops b/src/ops/experimental.ops
@@ -372,7 +372,7 @@ op receive(out PMC) {
             msg_count = VTABLE_elements(interp, pdata->mailbox);
 
         if (msg_count > 0) {
-            $1 = VTABLE_shift_pmc(interp, pdata->mailbox);
+            $1 = VTABLE_shift_pmc(pdata->interp, pdata->mailbox);
             Parrot_unblock_GC_mark(interp);
             UNLOCK(pdata->mailbox_lock);
             goto ADDRESS(dest);