Re: c/c++ project management and debugging

[Pascal J. Bourguignon]

Elena <egarrulo@gmail.com> writes:

> On Dec 22, 9:48 am, "Pascal J. Bourguignon" <p...@informatimago.com>
> wrote:
>> Elena <egarr...@gmail.com> writes:
>> > Moreover, when your heavily customized Emacs start to "misbehave" what
>> > can you do?  Start "emacs -Q" and begin evaluating sexps.  Oh, what an
>> > advanced debugging aid!  
>>
>> Contrarily to IDEs, emacs has a true debugger, and a true REPL, and a
>> whole lisp development environment.
>
> Pascal, talk is cheap, show me the debugger: my Emacs 23 hangs every
> few seconds.  How can I fix it with the help of such wonderful tools?

If you experiment hangs up, then you should debug them with gdb, because
they're bugs in the virtual machine.

If you have bug in emacs, then the first thing to do is 
M-x set-variable RET debug-on-error RET t RET
so that any error breaks into the emacs lisp debugger.


> "emacs -Q" followed by evaluating each sexp in my init file is not
> allowed.
>
> Where is your goddess now?  Have a nice day.


This is not my experience.  What I observe, is that emacs has an uptime
only limited by the uptime of the underlying system.

M-! uptime RET
 11:21:56 up 4 days,  8:01, 14 users,  load average: 0.85, 0.83, 0.82
(uptime) C-x C-e
 "Up 4d 6h 58m 47s (Sat 2010-12-18 04:23:14), 56 buffers, 5 files"


ssh voyager.informatimago.com uptime
 11:17:47 up 79 days,  6:51,  0 users,  load average: 0.11, 0.03, 0.01
ssh voyager.informatimago.com emacsclient -e '\(uptime\)'
".EMACS: Up 70d 6h 47m 51s (Wed 2010-10-13 05:30:20), 8 buffers, 1 files"



-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
A bad day in () is better than a good day in {}.