Re: recent commit breaks multi-module debugging

Bill Clementson <[email protected]> writes:

>> I still don't understand the need for the change. Do you have a
>> reproducible test case?
>
> Yes, see below.

That doesn't work for me at all. I gave up on the embedded erlang shell
very early on when i started using distel. I guess that's why ;)

When i get to the point in the script where the edb buffer should pop up
it just says "no more errors" in the mode-line, and the edb buffer shows
no processes. I can happily list processes, toggle interpretation etc,
so emacs is definitely talking to the node; debugging just isn't working
though.

By contrast, when I run your example in a separate node, started from a
shell, everything works fine. I can debug, stop and start the node,
continue debugging etc.

Perhaps the behaviour is different for me because I am running xemacs.

> The main problem occurs when you have done something to change the
> "state" of the erlang node that is being debugged. Once this happens,
> there is currently no way in distel to reset things.

For me, when the debugged node goes down, emacs kills the edb buffer and
resets the interpreted status of the modules I was debugging.

Does that not happen for you?

> I think there needs to be some way to "reset" debugging in distel. It
> would be nice if this could occur automatically (for example, when
> attaching to a node or when a connection to a debugged node is lost).

Well, it does do that for me.

> However, if this might cause problems, maybe it would be better to
> just have a separate function to reset debugging. What do you think?

What's wrong with just killing the edb buffer? That should work; it has
a hook that clears edb-interpreted-modules, resets breakpoints etc.


Matthias

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/