Re: debugger in 2.0?

[Neil Jerram]

Andy Wingo <address@hidden> writes:

> Hi Neil,

Hi Andy!

> I am going over the debugger section in the manual, and realizing that I
> duplicated a lot of your excellent work,

At least partly my fault for not being more in touch recently...

Incidentally, if you are thinking of (ice-9 debugger), I should point
out that that's not all my work; most of it already existed before I
joined Guile.

> and that the debugger situation
> is really in an uncomfortable half-equilibrium.

Yes, certainly.  But I think that was pretty inevitable, given the level
of core change for 2.0.

> And indeed, we don't
> debug as well on the expression level that we did in the past; I have
> some thoughts about that, but I don't think they should hold back 2.0.

I agree that they don't need to hold back 2.0.  We can add things back
during the 2.0.x series.  I guess we should be clear about the situation
in the release notes though.

> I wanted to write to say that I was considering combing (ice-9 debugger)
> for salvageable code, and pulling things over to (system vm debug).

Yes, that sounds good to me.

> I would refactor the manual section as well.

Even better!

> The VM debugger is not yet as
> nice as yours was, but it does work, and is closer to the VM
> implementation -- and the old one is broke. I feel bad about that, but
> it is how it is.
>
> Anyway, let me know if this is the wrong thing to do.

It's certainly right in the sense that the old stuff is broken, and so
some process is needed of seeing what can be reused from the 1.8 design
and code.

I actually made a bit of a start on this a few weeks ago when I was
looking at a UTF-16 problem, and I've just pushed this as
"wip-utf16-debugging" so that you can take a look.  I think the main
points of interest are:

- (gds-debug-vm) - attempt to connect the VM hooks to the GDS interface
  in Emacs

- updates in (ice-9 debugging traps) and (ice-9 gds-client) to cope with
  changes to frame-* API

- (ice-9 debugging new) - debugging by instrumentation instead of by
  using builtin hooks, as discussed a few weeks ago on the list

Please let me know if you think any of this is useful, and feel free to
incorporate in your own work.

When I was last working on this, the point that I reached was that the
VM->GDS hooks were working, but I was suffering from the lack (at the
time) of start-stack, and hence I was seeing too many hook calls from
infrastructure code before getting to the code that I was actually
trying to debug.  I guess that should be fixable now that start-stack is
back.

      Neil