From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#1077: bug#670: bug#1077: 23.0.60; x-create-frame: (wrong-type-argument number-or-marker-p nil) Date: Sun, 28 Nov 2010 21:54:14 +0200 Message-ID: <83fwul9qc9.fsf@gnu.org> References: <003e01c9257c$a385d800$0200a8c0@us.oracle.com> <009701c9263f$9cce7120$0200a8c0@us.oracle.com> <000001c94cc1$e10e9c40$0200a8c0@us.oracle.com> <8F1F8998D60341099C4204B7BDD8AD4F@us.oracle.com> <96BC00F728B94AC18A15EA95B66C5248@us.oracle.com> <83zksv5g7j.fsf@gnu.org> <0A475933984F4CDA855D91C8B7639E3B@us.oracle.com> <83fwum5xzk.fsf@gnu.org> <9F24875655894485A414CD785D95725B@us.oracle.com> <83bp595od5.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: dough.gmane.org 1290975318 23093 80.91.229.12 (28 Nov 2010 20:15:18 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 28 Nov 2010 20:15:18 +0000 (UTC) Cc: 1077@debbugs.gnu.org To: Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Nov 28 21:15:13 2010 Return-path: Envelope-to: geb-bug-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 1PMneS-00041V-3G for geb-bug-gnu-emacs@m.gmane.org; Sun, 28 Nov 2010 21:15:12 +0100 Original-Received: from localhost ([127.0.0.1]:52384 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PMneR-0001KB-7y for geb-bug-gnu-emacs@m.gmane.org; Sun, 28 Nov 2010 15:15:11 -0500 Original-Received: from [140.186.70.92] (port=33660 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PMneH-0001H9-QI for bug-gnu-emacs@gnu.org; Sun, 28 Nov 2010 15:15:02 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PMneF-0006Mb-ES for bug-gnu-emacs@gnu.org; Sun, 28 Nov 2010 15:15:01 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:60427) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PMneF-0006MX-D1 for bug-gnu-emacs@gnu.org; Sun, 28 Nov 2010 15:14:59 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.69) (envelope-from ) id 1PMnDC-00062F-8o; Sun, 28 Nov 2010 14:47:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-To: owner@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 28 Nov 2010 19:47:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 1077 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 1077-submit@debbugs.gnu.org id=B1077.129097360023169 (code B ref 1077); Sun, 28 Nov 2010 19:47:02 +0000 Original-Received: (at 1077) by debbugs.gnu.org; 28 Nov 2010 19:46:40 +0000 Original-Received: from localhost ([127.0.0.1] helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1PMnCp-00061e-Fn for submit@debbugs.gnu.org; Sun, 28 Nov 2010 14:46:39 -0500 Original-Received: from mtaout20.012.net.il ([80.179.55.166]) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1PMnCm-00061R-P5 for 1077@debbugs.gnu.org; Sun, 28 Nov 2010 14:46:37 -0500 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0LCM00G001R85W00@a-mtaout20.012.net.il> for 1077@debbugs.gnu.org; Sun, 28 Nov 2010 21:52:07 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([84.229.63.39]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LCM00FW11URTC20@a-mtaout20.012.net.il>; Sun, 28 Nov 2010 21:52:05 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.11 Precedence: list Resent-Date: Sun, 28 Nov 2010 14:47:02 -0500 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:41979 Archived-At: > From: "Drew Adams" > Cc: <1077@debbugs.gnu.org> > Date: Sun, 28 Nov 2010 10:42:50 -0800 > > I have 7zip, and that worked. I put the binaries in my PATH. Next time I get a > crash I should be able to use GDB, I guess. It's a good idea to download the file src/.gdbinit as well, and have it handy. You should start GDB in the directory where you keep .gdbinit, so that GDB will automatically read it at startup. That file has many useful commands that make debugging Emacs and printing the various objects and data structures much easier. Let me know if you want me to send you that file, in case you have difficulties getting it from the repository. > > > Then why doesn't the Lisp debugger have a stack frame for > > > the Lisp function that called `<'? I assume you're saying that > > > C calls some Lisp function _besides_ the Lisp function `<'. > > > Why doesn't that function appear in the backtrace? > > > > Lisp debugger has no visibility into the C level. > > I understand that. But I'm not clear on how the backtrace stack is constructed. > If the error occurs in `<' (Lisp), then shouldn't Lisp know what the _Lisp_ > caller of Lisp `<' was? (You've already mentioned, I think, that C doesn't > return control to Lisp `<' directly.) By now you will have seen my initial analysis of the problem, so you know the reason: `<' was called directly from C, via the `eval' primitive, when the code which builds the menu bar evaluated the properties of the menu items. IOW, I was mistaken, it's not called by some other Lisp. > But `C-M-down' is _not_ bound to `down-list' in the minibuffer completion maps > in Icicle mode. If you are really in Icicle mode, then `C-M-down' is bound (by > default) to `icicle-next-candidate-per-mode-help' in the minibuffer completion > maps. If it is bound to that command, then you should be able to see the > backtrace I reported when you hit `C-M-down'. Maybe the reason is that I typed `ESC C-down', not C-M-down. I don't think it's important at this time, since C-M-End reproduces the problem.