I find Distel[1], which extends emacs, to be a very good IDE for erlang. It connects to a running erlang VM and accesses the code module, to produce support for symbolic debugging, listing processes, etc.. There is a bug in who_calls, one of the more valuable features. You can work around it by invoking who_calls once from the VM directly, .eg. distel:who_call(couch_uuids,new,0). and thereafter C-c C-d w will do the right thing. This is very useful for navigating the code paths.
There are some docs[2] that aren't complete, but will get you started Best, Bob [1] http://github.com/kunley/distel [2] http://github.com/kunley/distel/tree/master/doc/ On Sep 13, 2010, at 6:31 PM, Konstantin Weitz wrote: > Hi all, > > On my path to gain unlimited wisdom, I'm working on get a better understanding > of couchdb. I'm especially interested in (the) erlang (impelementation). I got > the svn version installed and running on my ubuntu 10.4 and followed the code > through a couple of files, but it is rather stressfull to io:format out > everything > and recompile to keep track of my current location. > What Development Setups do you use? Especially a debugger, which I could use > to > step throught the code, would be nice (I tryed using the one that one can > start > using debugger:start(), but it seems to be very unrelaxed to compile every > single module with debugging info and attach it to the debugger by hand). > > Any input on how to do this would be great. > > > {"name": "Konstantin Weitz"}
