From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Leo Alekseyev Newsgroups: gmane.emacs.help Subject: C-h f strange behavior with 24.1.50 snapshot Date: Thu, 5 Jul 2012 02:43:22 -0500 Message-ID: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: dough.gmane.org 1341474218 2078 80.91.229.3 (5 Jul 2012 07:43:38 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 5 Jul 2012 07:43:38 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Jul 05 09:43:36 2012 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 1Smgis-0004e6-8l for geh-help-gnu-emacs@m.gmane.org; Thu, 05 Jul 2012 09:43:34 +0200 Original-Received: from localhost ([::1]:53421 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Smgir-0002K7-5e for geh-help-gnu-emacs@m.gmane.org; Thu, 05 Jul 2012 03:43:33 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:32964) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Smgil-0002Jv-JM for help-gnu-emacs@gnu.org; Thu, 05 Jul 2012 03:43:29 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Smgij-0008Nn-IC for help-gnu-emacs@gnu.org; Thu, 05 Jul 2012 03:43:27 -0400 Original-Received: from mail-vb0-f41.google.com ([209.85.212.41]:36002) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Smgij-0008Mo-Ar for help-gnu-emacs@gnu.org; Thu, 05 Jul 2012 03:43:25 -0400 Original-Received: by vbkv13 with SMTP id v13so6344970vbk.0 for ; Thu, 05 Jul 2012 00:43:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=ritvX1dCAX6TkUSxtZDa6x3ZOt6No7W6QmhWKyoe91s=; b=isAwdCavBbxujH27Da/0btq3A1bp/kC2eod3C2y4AzfXLz/0RadVGBXFsj6kxPvYSj i7LHtp1YF94606PwbgN68EZkJ27sckIlT20vX6lpvvqvp8MzW2gJEodSwVIyvbiZaogu wbufibf27MPocCnTwW0mXG6vDBoSvYqYChDQn067DT4ErfhHZFiZbkgX55pnMJZEtTrb MuEarzEVw2hq4N8mhSjdZgTQFsGtNax2iAuvuJ6l4lvUQpI5/RbIk8+XP8wGBsFP92To SsXn1LC3b8JNprAo7wWP3FAGC5HYT4Wg66LNs2HMy8glOK+2/p957nq0WYUnasKax73T 4gTw== Original-Received: by 10.220.153.82 with SMTP id j18mr11965343vcw.40.1341474202822; Thu, 05 Jul 2012 00:43:22 -0700 (PDT) Original-Received: by 10.52.112.38 with HTTP; Thu, 5 Jul 2012 00:43:22 -0700 (PDT) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 209.85.212.41 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:85671 Archived-At: I'm running a 2012-07-01 snapshot from Damien Cassou's Ubuntu PPA and am seeing C-h f breaking /on one of my machines/ with : help-fns--autoloaded-p: Wrong type argument: arrayp, nil The function names which cause this breakage seem to be dependent in some non-trivial fashion on what I have loaded in my .emacs. For instance, with blank .emacs, e.g. C-h f dired works, but if I load one of (emacs-nav [[http://code.google.com/p/emacs-nav/]], dired-extension [[http://www.emacswiki.org/emacs/dired-extension.el]]) it throws the error. I haven't been able to figure out what in these packages causes the error. If I do emacs -Q, I can reproduce this error by doing : C-h f help-fns--autoloaded-p What makes this bizarre is that between my two machines, both running Ubuntu 12.04 64-bit, both with freshly installed emacs-snapshot from the PPA, only _one_ exhibits the breakage. How would I try to isolate the problem further? In general, how does one go about getting more information about such errors? Can one enable a more detailed traceback, like one provided by --debug-init, but something that would get triggered by errors such as the one above?