From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Elena Newsgroups: gmane.emacs.help Subject: Re: c/c++ project management and debugging Date: Wed, 22 Dec 2010 04:34:16 -0800 (PST) Organization: http://groups.google.com Message-ID: <86126496-de72-4e5c-9443-5cfce30f28ab@15g2000vbz.googlegroups.com> References: <4D0F4058.6050101@gmail.com> <038dfa58-3e80-4c49-bbd0-c1bbb16c41f1@j25g2000vbs.googlegroups.com> <87bp4ex0a4.fsf@kuiper.lan.informatimago.com> <7e99bd12-91df-4cc2-bfc9-576df4c5283b@i18g2000yqn.googlegroups.com> <87k4j2uohx.fsf@kuiper.lan.informatimago.com> <6d58027e-6ed1-41f6-8653-fbcd42236b68@w2g2000yqb.googlegroups.com> <87fwtqums7.fsf@kuiper.lan.informatimago.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1293021641 25024 80.91.229.12 (22 Dec 2010 12:40:41 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 22 Dec 2010 12:40:41 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Dec 22 13:40:37 2010 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PVNzh-0008E1-D1 for geh-help-gnu-emacs@m.gmane.org; Wed, 22 Dec 2010 13:40:37 +0100 Original-Received: from localhost ([127.0.0.1]:42975 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PVNzg-0005jQ-Ta for geh-help-gnu-emacs@m.gmane.org; Wed, 22 Dec 2010 07:40:36 -0500 Original-Path: usenet.stanford.edu!postnews.google.com!15g2000vbz.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 47 Original-NNTP-Posting-Host: 89.96.190.244 Original-X-Trace: posting.google.com 1293021256 25414 127.0.0.1 (22 Dec 2010 12:34:16 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Wed, 22 Dec 2010 12:34:16 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: 15g2000vbz.googlegroups.com; posting-host=89.96.190.244; posting-account=AFCLjAoAAABJAOf_HjgEEEi3ty-lG5m2 User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13,gzip(gfe) Original-Xref: usenet.stanford.edu gnu.emacs.help:183541 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:77783 Archived-At: On Dec 22, 10:25=A0am, "Pascal J. Bourguignon" wrote: > Elena writes: > > On Dec 22, 9:48=A0am, "Pascal J. Bourguignon" > > wrote: > >> Elena writes: > >> > Moreover, when your heavily customized Emacs start to "misbehave" wh= at > >> > can you do? =A0Start "emacs -Q" and begin evaluating sexps. =A0Oh, w= hat an > >> > advanced debugging aid! =A0 > > >> 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. =A0How 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. No need to bring in the bigger guns. It could just be some scheduled activity by who-knows what package. If Emacs Lisp had both a tracing and a profiling utility, I would have squashed the bug already. > 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. Oh, already done. That's easy. No error whatsoever. > > > "emacs -Q" followed by evaluating each sexp in my init file is not > > allowed. > > > Where is your goddess now? =A0Have a nice day. > > This is not my experience. =A0What I observe, is that emacs has an uptime > only limited by the uptime of the underlying system. "emacs -Q" is effective in deciding whether something comes from Emacs' default behavior or from some package. Once you have decided it must be some package, that's the hairy part where Emacs debugging tools aren't up to the task. That's why I have said that users have pushed Emacs beyond its capabilities: IDE, mail-reader... guys, here we have just a simple text editor which doesn't pretend to by anything else.