PDB [Was: Re: Calling conventions, IMC]

[Will Coleda]

Ok. I've converted my code over to do this[1]. I am now able to compile tcl.imc, but all my code fails to run, ala:

bash-2.05a$ make exit
../../../parrot ../tcl.pbc exit.tcl
branch_cs: illegal resume offsetmake: *** [exit] Error 1

So, I'm trying to track down where this badness is happening:

bash-2.05a$ ../../pdb tcl.pbc
Parrot Debugger 0.0.2

(pdb) run examples/exit.tcl
Restarting

And it hangs.

if I hit ^D, it closes. This smells like it's ignoring the command line argument and running the pbc with no args, which forces it to read tcl from STDIN. (...dig... yup, that's what it's doing.)

So, how can I convince pdb to pass along the args to my bytecode?

Also, if I do:

bash-2.05a$ ../../pdb tcl.pbc
Parrot Debugger 0.0.2

(pdb) load tcl.imc

(pdb) list 1 100

I get 32 1/2 lines of output before getting a segfault. (I've attached the crash log)

list by itself works fine. There doesn't seem to be a specific X for "list 1 X" where it consistently segfaults, but anything > 12 seems to do a pretty good job.

Regards.

crash.log
Description: Binary data

[1]
On Monday, January 19, 2004, at 05:16  PM, Luke Palmer wrote:

Will Coleda writes:

If I can't explicitly create foo_sub if I'm in the middle of __foo, how
do I recurse using calling conventions

You could use P0, which holds the subroutine object.  Like using &_ in
Perl 6.

Luke

--
Will "Coke" Coleda will at coleda dot com