Re: Questions

"Kirill Zaborski" <[email protected]> writes:

> I was trying to get Erlang debugging with distel working (thanx Bill
> Clementson). But something goes wrong...
> I start a function then press ENTER  and receive message:
> "nodedown: emacs@dkzh991"
> and presing "n" (or SPC) generates message:
> "if: peculiar error: [badarg [not-registered nil]]"
>
> Looks like something isn't set up correctly but what?

Since it wants to connect to the "emacs@..." node, it looks like
you've followed the same naming convention that I used to specify the
node for the Erlang Shell in Emacs. Since it's giving a "nodedown"
error message, that means that it can't communicate with it. Perhaps
you might have deleted the Erlang Shell buffer (breaking the
connection). If you closed the shell and re-started it, you will
probably need to reconnect to the node with "C-c C-d n".

> And also I see that sometimes breakpoint lines get colored in blue
> (not orange as normaly) and they don't work - what does it mean and
> how can I fix it?

Your source buffer is probably out of sync with the debug info for the
program. In the source buffer, try re-loading the module ("C-c C-d L")
and/or synchronizing breakpoints ("C-c C-d s").

Good luck!

--
Bill Clementson


-------------------------------------------------------------------------
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/