Re: recent commit breaks multi-module debugging

Bill Clementson <[email protected]> writes:

> I was encountering it on a regular basis. However, I often debug in
> the Emacs Erlang shell node and not in a separate Erlang node so maybe
> that might be a factor.

Ah, I never do that.

> How would my new patch break multiple module debugging? If all modules
> are running in the same node, it should have no impact at all. Did you
> mean "across multiple *nodes*"?

Yes, I did mean that. Sorry about the confusion.

> If so, then yes my patch would reset the distel interpreted status
> every time you switched nodes. However, the break points that are set
> in the node would still exist. When you switch from one node to
> another, you would need to toggle on interpreted status for a buffer.

That doesn't sound too bad. How does this differ from the previous
behaviour?

I still don't understand the need for the change. Do you have a
reproducible test case?

Looking at the code, it seems that edb-start-monitor should update the
interpreted status of modules in distel with that of the node. This
suggests that manual toggling when switching nodes shouldn't actually be
necessary. Also take a look at edb-ensure-monitoring and
edb-monitor-node-change-p, which both supposedly deal with node
switching.


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/