Re: Questions

On 6/4/07, Kirill Zaborski <[email protected]> wrote:
> On 6/5/07, Bill Clementson <[email protected]> wrote:
> Hi Kirill,
> >
> > I think I've found the problem (at least, the problem I was
> > experiencing). Apply the attached patch to distel/elisp/edb.el and let
> > me know if this helps matters for you. Please do the following steps
> > to see if it works:
> >
> > 1. Open an erlang file (say "myfile.erl") in an emacs buffer and start
> > up an erlang shell. In the erlang node (shell), do: c("myfile.erl",
> > [debug_info]).
> > 2. In your emacs myfile.erl buffer, press "C-c C-d n" and specify the node
> > 3. In your emacs myfile.erl buffer, press "C-c C-d L" to reload
> > 4. In your emacs myfile.erl buffer, press "C-c C-d i" to toggle
> > interpreting. If it says that interpreting is stopped, press "C-c C-d
> > i" 1 more time to start interpreting. However, if it says that
> > interpreting is started, press "C-c C-d i" 2 more times to stop and
> > re-start interpreting.
> > 5. In your emacs myfile.erl buffer, put the cursor on a source line
> > and press "C-x SPC" to set a breakpoint. If the breakpoint is
> > highlighted in orange - GREAT! If it's highlighted in blue - press
> > "C-c C-d s" to sync the breakpoint.
> > 6. In the erlang node (shell), run an erlang function that will hit
> > the breakpoint.
> >
> > At this point (hopefully), you should be debugging erlang code in
> > emacs. There are probably some things that can be done to streamline
> > the above process; however, if you try the steps exactly as I outlined
> > them above, that should tell me whether the fix is working for you.
> >
>
> Thanks for your efforts Bill but it doesn't work for me.
> I've applied the patch and run all the steps. When I tried to turn off
> (after turning it on) the interpreting mode 'nodedown' message
> appeared - the rest was the same as before.
> I've tried to use stand-alone node with the same result.
> It looks like emacs can not find the node for debugging. But
> expression evaluation works quite fine and process list also.

That's odd - I never got any nodedown messages. My problem was that
the debugger would sometimes "stop working". At least one other person
had similar symptoms to the ones that I was having (and which I think
I've fixed): http://thread.gmane.org/gmane.comp.lang.erlang.distel.devel/18/focus=24
>From his description, it sounded like your symptoms might have been similar.

Looking through some of the other debugger-related messages on the
list, it would appear that potential problem areas might be:

1. MS Windows seems to have been problematic in the past. What OS are
you running?
2. At one stage, the debugger wanted the node entered as
"node@address" whereas other apps would work ok with just "node";
however, I thought that was fixed - you might want to try specifying
the long format for the node
3. Re-booting emacs (horrors!) and then setting distel up directly for
debugging (without doing anything else) worked for me at least once in
the past
4. What version of Distel are you running? Did you download it from
the google code subversion repository
(http://code.google.com/p/distel/)? Older versions were (and may still
be) on sourceforge and jungerl but you should be using the google code
version.
5. If you upgraded Erlang, did you re-build the erlang source files
that are part of Distel? It probably doesn't matter; however, we're
grasping at straws
6. Did you double-check your .emacs file setup to make certain that
the erlang-root-dir, load-path, exec-path, and distel-dir variables
all point to the correct locations for both erlang.el and distel? If
they are pointing to old locations, you probably forgot to update them
after an OTP upgrade.
7. You indicated previously that distel debugging worked ok on your
home machine but not on your work machine. How do the two differ? Are
they the same OS, same versions of erlang & distel?

If none of the above helps solve the problem for you, can you provide
a simple, reproducible set of steps that you can do to consistently
replicate the problem? Preferably, the exact keystrokes that you use.
If so, I'll see whether I have the same issue on my machine.

- Bill

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