Ok, makes sense. It seems like it would be best to have technical
discussions archived as much as is possible, so let's move this to
debug-commons.
On 9/24/07, Martin Krauskopf <[EMAIL PROTECTED]> wrote:
>
> Chris Nelson wrote:
> > Well, after all that whining it appears to be not so dire. I simply
> > commented out the call to getFrameArgs() and that got me all the way to
> > setting up a simple bug session! I'm stepping thru code and printing
> > variables in rdebug. Woot!!
> >
> > Martin, can you give me some insight on what getArgc in DebugFrame is
> > used for? I couldn't find any references to it. This is the only thing
> > that was using getFrameArgs()
>
> I suppose, it was just a rewrite of save_call_frame from ruby_debug.c.
> Might be good, might be wrong. I started with bare skeleton having:
>
> throw new UnsupportedOperationException("not implemented yet");
>
> in most of the method. Then trying to run tests, then simple debug
> session and always when I got UOE I'd rewritten the method from
> ruby_debug.c. There are still some UOE in the code. So in this case just
> commenting out works.
> I've committed and also throwing UOE from DebugFrame.getArgc() - seems
> to be not called so far after short try.
>
> Probably we should moved those discussion somewhere else, they are
> really specific to the ruby-forge project. Either to debug-commons forum
> or let's mail directly.
>
> Regards,
> m.
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
