eval is broken in parrot_debugger

[dukeleto]

$ ./parrot_debugger

Parrot 1.4.0-devel Debugger

Please note: the debugger is currently under reconstruction

(pdb) e I0=2

too few arguments passed to NCI function

current instr.: 'aux' pc 0 (EVAL_1:2)

[dukeleto]

I have traced this to the call to VTABLE_invoke(interp, compiler, buf) in PDB_compile() in src/debug.c :

PARROT_CAN_RETURN_NULL
opcode_t *
PDB_compile(PARROT_INTERP, ARGIN(const char *command))
{
    ASSERT_ARGS(PDB_compile)
    STRING     *buf;
    const char *end      = "\nend\n";
    STRING     *key      = CONST_STRING(interp, "PASM");
    PMC *compreg_hash    = VTABLE_get_pmc_keyed_int(interp,
            interp->iglobals, IGLOBALS_COMPREG_HASH);
    PMC        *compiler = VTABLE_get_pmc_keyed_str(interp, compreg_hash, key);

    if (!VTABLE_defined(interp, compiler)) {
        fprintf(stderr, "Couldn't find PASM compiler");
        return NULL;
    }

    buf = Parrot_sprintf_c(interp, "%s%s", command, end);

    return VTABLE_invoke(interp, compiler, buf);   <---- BOOM
}

The VTABLE_invoke call generates the NCI error.

[NotFound]

See TT #872

[dukeleto]

From #parrot 4. august 2009

[1:58am] <dukeleto>
chromatic: do you have any ideas about implementing PDB_eval in something close to Parrot's current state? or will it require some large changes?
...
[1:59am] <chromatic> We'd have to get a self-hosted PIR compiler working better first.
[1:59am] <chromatic> That's not likely to happen in the next couple of months.

It seems that this ticket is stalled until some other things can be sorted out correctly.

[bacek]

Replying to dukeleto:

From #parrot 4. august 2009 {{{ [1:58am] <dukeleto> chromatic: do you have any ideas about implementing PDB_eval in something close to Parrot's current state? or will it require some large changes? ... [1:59am] <chromatic> We'd have to get a self-hosted PIR compiler working better first. [1:59am] <chromatic> That's not likely to happen in the next couple of months. }}} It seems that this ticket is stalled until some other things can be sorted out correctly.

Can I say something not-quite-polite?

1. #894 2.  http://github.com/bacek/pir/commits/

-- Bacek

[dukeleto]

Bacek,

Could you please swear at me more directly? ;)

What needs to be done in your pir repo? I am still trying to get past parrot_config being hardcoded...

[jkeenan]

bacek, dukeleto:

Can we get an update on the status of the issues discussed in this ticket?

Thank you very much.

kid51

[dukeleto]

Current debugger is not worth saving, and deprecated.