From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.help Subject: RE: (debug) backtrace: how to show source code at current location. Date: Wed, 5 Jan 2011 11:06:59 -0800 Message-ID: <4678E0C82C5D4DAB81AF90DFA7E07027@us.oracle.com> References: 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 1294254496 20283 80.91.229.12 (5 Jan 2011 19:08:16 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 5 Jan 2011 19:08:16 +0000 (UTC) To: "'Larry Evans'" , Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Jan 05 20:08:11 2011 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 1PaYiR-0001GM-2v for geh-help-gnu-emacs@m.gmane.org; Wed, 05 Jan 2011 20:08:11 +0100 Original-Received: from localhost ([127.0.0.1]:59247 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PaYiQ-0006G2-Ii for geh-help-gnu-emacs@m.gmane.org; Wed, 05 Jan 2011 14:08:10 -0500 Original-Received: from [140.186.70.92] (port=38401 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PaYhs-0006FH-Au for help-gnu-emacs@gnu.org; Wed, 05 Jan 2011 14:07:37 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PaYhp-0000HH-Cu for help-gnu-emacs@gnu.org; Wed, 05 Jan 2011 14:07:36 -0500 Original-Received: from rcsinet10.oracle.com ([148.87.113.121]:56127) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PaYhp-0000H1-6i for help-gnu-emacs@gnu.org; Wed, 05 Jan 2011 14:07:33 -0500 Original-Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p05J7Uu4030753 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 5 Jan 2011 19:07:32 GMT Original-Received: from acsmt354.oracle.com (acsmt354.oracle.com [141.146.40.154]) by rcsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p05Em0WZ022535; Wed, 5 Jan 2011 19:07:28 GMT Original-Received: from abhmt009.oracle.com by acsmt355.oracle.com with ESMTP id 901783251294254418; Wed, 05 Jan 2011 11:06:58 -0800 Original-Received: from dradamslap1 (/130.35.178.194) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 05 Jan 2011 11:06:58 -0800 X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcutA5b/VTf5YN7uRe6A+FNsh2Ua0AAA3FmA In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) 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:78222 Archived-At: > Please, how can I find out what's causing this error message: >=20 > "(wrong-type-argument arrayp tab)" >From your error message alone, it seems that the symbol `tab' is being = passed to some function that expects an array. That's not much help yet, but = things might become clearer when you dig deeper using the debugger. (setq debug-on-error t) 1. Load source (*.el) files for the library where the error occurred. IOW, look at the `debug-on-error' backtrace to see which function(s) = were involved when the error occurred. Then use `C-h f' or `find-func' to = find the function definition(s) (source file(s)). Load the source file(s) (*.el) = using `load-file' or `load-library', including the extension `.el' in the = name. 2. Provoke the error and backtrace again. It should now show more = source-code entry points instead of byte-code (the `(byte-code "=C1=C2=C3...' stuff) 3. You can also use `M-x debug-on-entry THE-FUNCTION' to enter the = debugger whenever a problematic function is invoked. Then you can walk through = the invocation to see more about what caused the error.