Ticket #901 (closed bug: wontfix)

Opened 5 years ago

Last modified 3 years ago

eval is broken in parrot_debugger

Reported by: dukeleto Owned by: dukeleto
Priority: normal Milestone:
Component: core Version: 1.4.0
Severity: medium Keywords: debugger
Cc: Language:
Patch status: Platform:

Description

$ ./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)

Change History

  Changed 5 years ago by 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.

  Changed 5 years ago by NotFound

See TT #872

follow-up: ↓ 4   Changed 5 years ago by 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.

in reply to: ↑ 3 ; follow-up: ↓ 5   Changed 5 years ago by 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

in reply to: ↑ 4   Changed 5 years ago by 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...

  Changed 5 years ago by dukeleto

  • status changed from new to assigned

  Changed 5 years ago by dukeleto

  • component changed from none to core
  • milestone 1.7 deleted

  Changed 4 years ago by jkeenan

bacek, dukeleto:

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

Thank you very much.

kid51

  Changed 3 years ago by jkeenan

  • keywords debugger added

  Changed 3 years ago by dukeleto

  • status changed from assigned to closed
  • resolution set to wontfix

Current debugger is not worth saving, and deprecated.

Note: See TracTickets for help on using tickets.