From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: bolega Newsgroups: gmane.emacs.help Subject: Re: An instructive example of trace-function and some example of debugging Date: Sat, 12 Jun 2010 10:42:14 -0700 (PDT) Organization: http://groups.google.com Message-ID: References: <1af7c938-1f8d-414c-8970-f82961c8b0cd@y11g2000yqm.googlegroups.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 1291840452 24415 80.91.229.12 (8 Dec 2010 20:34:12 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 8 Dec 2010 20:34:12 +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 08 21:34:08 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 1PQQiG-0005xu-3A for geh-help-gnu-emacs@m.gmane.org; Wed, 08 Dec 2010 21:34:08 +0100 Original-Received: from localhost ([127.0.0.1]:37643 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PQQiF-0001jF-6x for geh-help-gnu-emacs@m.gmane.org; Wed, 08 Dec 2010 15:34:07 -0500 Original-Path: usenet.stanford.edu!postnews.google.com!a30g2000yqn.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 38 Original-NNTP-Posting-Host: 75.28.103.27 Original-X-Trace: posting.google.com 1276364534 22791 127.0.0.1 (12 Jun 2010 17:42:14 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Sat, 12 Jun 2010 17:42:14 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: a30g2000yqn.googlegroups.com; posting-host=75.28.103.27; posting-account=REkl4woAAABFXaU7nL79XtGpnmNCQ415 User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6,gzip(gfe) Original-Xref: usenet.stanford.edu gnu.emacs.help:178869 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:75989 Archived-At: On Jun 10, 1:27=A0pm, bolega wrote: > An instructive example of trace-function and some example of > debugging, for example, some of the error that pops up in lower window > of emacs and how to read/interpret it. Alternatively, a link to some > page or elisp manual but I am sure an expert here would have a > superior instruction as many replies here have shown. > > Thanks > Bolega > > trace-function is an interactive autoloaded Lisp function in `trace'. > [Arg list not available until function definition is loaded.] > > Traces FUNCTION with trace output going to BUFFER. > For every call of FUNCTION Lisp-style trace messages that display > argument > and return values will be inserted into BUFFER. This function > generates the > trace advice for FUNCTION and activates it together with any other > advice > there might be!! The trace BUFFER will popup whenever FUNCTION is > called. > Do not use this to trace functions that switch buffers or do any other > display oriented stuff, use `trace-function-background' instead. Sometimes, in emacs, error takes places and the mode gets nested inside many brackets. [(((.lisp...)))] above line recalling from memory what does it mean ? C-g does not get out of it. What to do ?