Re: recent commit breaks multi-module debugging

Bill,

Bill Clementson <[email protected]> writes:

> Matthias Radestock <[email protected]> writes:
>
>> What is the value of edb-interpreted-modules / the 'interpreted' status 
>> as shown in the modeline after the following?
>>
>> 1) kill node that is being debugged -> nil/not-interpreted for me.
>
> same for me 
>
>> 2) restart node -> nil/not-interpreted for me.
>
> same for me
>
>> 3) reload module -> nil/not-interpreted for me.
>
> same for me - have to do "C-c C-d L" twice (first time loads distel modules into node)

I think this may be the source of the problem. I only have to hit "C-c
C-d L" *once*, which is the correct behaviour.

> 1. kill node that is being debugged
> 2. restart node
> 3. toggle interpreting on with "C-c C-d i" twice 
>    (first time loads distel modules into node) 
>    **note that I didn't reload the module into the node before toggling
>    interpreting on**. 
>    I get a minibuffer message that interpreting is on (but nothing in 
>    mode line).

When I hit "C-c C-d C-i" *once* (this, I think, may be the key
difference) I get the message "Interpreting: module-name" in the
minibuffer, and the modeline shows "<interpreted>".

Hitting "C-c C-d C-i" again turns interpreting off, so I've skipped that
and continued with ...

> 4. toggle interpreting off with "C-c C-d i". 
>    I get a message that interpreting is off (but nothing in 
>    mode line).

I get the message "Stopped interpreting: module-name" in the
minibuffer and the modeline no longer shows "<interpreting>".

> 5. reload module with "C-c C-d L"
> 6. toggle interpreting on with "C-c C-d i" 
>    I get a minibuffer message that interpreting is on (but nothing in 
>    mode line).

I get the same result as when turning interpreting on the first time
round, i.e. a minibuffer message and change in modeline.

> at this point, you can't toggle interpreting on/off at all (e.g. -
> nothing shows up in the mode line although you do get minibuffer
> messages indicating that interpreting is on/off) and trying to set a
> breakpoint results in the "Module is not interpreted, can't set
> breakpoints." error message).

I do not see this behaviour. Everything is working fine for me at this
point. I can happily toggle interpreting and set breakpoints.

> So, perhaps the underlying issue relates to how (or whether) the
> module has been loaded into the node before interpreting is turned on
> for the first time.

I think the issue is related to the loading of the *distel* modules. See
my reply to your other post. As I said there, the difference between
your and my setup might be that I have distel on my Erlang load path and
perhaps you don't. Let's continue in that new thread and return to this
one when have found a solution there.


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/