From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Gracjan Polak Newsgroups: gmane.emacs.help Subject: Re: Wrong type argument: arrayp, nil Date: Sun, 20 Apr 2014 20:25:20 +0200 Message-ID: References: <840abf5d-4b46-4630-a416-4df26b8f7770@default> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1398040767 21942 80.91.229.3 (21 Apr 2014 00:39:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 21 Apr 2014 00:39:27 +0000 (UTC) Cc: help-gnu-emacs@gnu.org To: Drew Adams Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Apr 21 02:39:22 2014 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Wc2GY-0005TJ-1m for geh-help-gnu-emacs@m.gmane.org; Mon, 21 Apr 2014 02:39:22 +0200 Original-Received: from localhost ([::1]:47076 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wc2GX-00064e-LW for geh-help-gnu-emacs@m.gmane.org; Sun, 20 Apr 2014 20:39:21 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57580) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WbwQx-0002YV-So for help-gnu-emacs@gnu.org; Sun, 20 Apr 2014 14:25:44 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WbwQw-0004qM-QD for help-gnu-emacs@gnu.org; Sun, 20 Apr 2014 14:25:43 -0400 Original-Received: from mail-wg0-x22a.google.com ([2a00:1450:400c:c00::22a]:44914) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WbwQw-0004q7-IT for help-gnu-emacs@gnu.org; Sun, 20 Apr 2014 14:25:42 -0400 Original-Received: by mail-wg0-f42.google.com with SMTP id y10so2023642wgg.25 for ; Sun, 20 Apr 2014 11:25:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=jfOlE1t5gTIqvEc6BR3nLaLEVCND4aOrsnqUKLACz7o=; b=qXnJxeFB2rkihfhNzVq6Qb8BvwjohMEx8DJOQ4GTORU4X+CE29dn6LsZNL7vYglj2V /3Kc4M3PTSHu3iDayQMY0SnNS+LziCyKD4k9Ok4nnW6ShqJPH1CZe8Zdm16MUt1zusOM xgqRyU4R9u538/A1qam7VK/cSk9zWPhXqXB9NJixzulk9WsSdqa+MFE5N1S24RDbtqQk fTpGLVktfL0Y3lJHjLf76SO0TvLXH5OzETdbeUSq60CH6TeZoO/la8t77xdvMKUI/3el suOWgetSDOI+WkJHiIN7UyaYv1Izvy0QcKuCuaNoCVV/6+g2SW9ifrr/P4tme7DXg730 AjDw== X-Received: by 10.180.14.199 with SMTP id r7mr10761927wic.0.1398018340788; Sun, 20 Apr 2014 11:25:40 -0700 (PDT) Original-Received: by 10.194.8.65 with HTTP; Sun, 20 Apr 2014 11:25:20 -0700 (PDT) In-Reply-To: <840abf5d-4b46-4630-a416-4df26b8f7770@default> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c00::22a X-Mailman-Approved-At: Sun, 20 Apr 2014 20:39:05 -0400 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:97278 Archived-At: Thanks, that got me started. Is there a debug tutorial somewhere or d and c and q is all that is needed in real life? How does you debug-edit-debug cycle look like? Is C-x C-e all I should be using or is there something that has a concept of 'a breakpoint'? 2014-04-20 20:16 GMT+02:00 Drew Adams : > First, do this, to get a human-readable backtrace: > > 1. Set variable `debug-on-error' to t. > 2. Provoke the error, so you can see which function is problematic. > Quit the debugger using `q'. > 3. Load the source files for the package in question. This is to > give you a more human-readable backtrace. > 4. Provoke the error again. > > You can now report the problem to the package maintainer. If the > responsible code is delivered as part of Emacs (not some 3rd party) > then report the problem to Emacs Dev using `M-x report-emacs-bug'. > > If you want to debug it further yourself, step through the debugger > after step #4 above. Use `d' to single-step and `c' to skip through > a step. Use `q' to quit or step through until the problematic > function returns. > > Some people prefer `edebug' to `debug'. I prefer `debug', which is > what you get with the above recipe. >