From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Emacs aborts during byte-compilation from Dired Date: Thu, 22 Feb 2007 12:50:33 +0100 Message-ID: <86y7mqwgvq.fsf@lola.quinscape.zz> References: <877iuablng.fsf@pacem.orebokech.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1172145059 721 80.91.229.12 (22 Feb 2007 11:50:59 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 22 Feb 2007 11:50:59 +0000 (UTC) Cc: Romain Francoise , emacs-devel@gnu.org To: Kenichi Handa Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 22 12:50:52 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1HKCTJ-0002gw-Bw for ged-emacs-devel@m.gmane.org; Thu, 22 Feb 2007 12:50:49 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HKCTJ-0003Yh-20 for ged-emacs-devel@m.gmane.org; Thu, 22 Feb 2007 06:50:49 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HKCT7-0003Yc-Tg for emacs-devel@gnu.org; Thu, 22 Feb 2007 06:50:37 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HKCT6-0003YQ-I0 for emacs-devel@gnu.org; Thu, 22 Feb 2007 06:50:36 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HKCT6-0003YN-CZ for emacs-devel@gnu.org; Thu, 22 Feb 2007 06:50:36 -0500 Original-Received: from pc3.berlin.powerweb.de ([62.67.228.11]) by monty-python.gnu.org with esmtp (Exim 4.52) id 1HKCT5-0006uv-Ln for emacs-devel@gnu.org; Thu, 22 Feb 2007 06:50:36 -0500 Original-Received: from quinscape.de (pd95b0fdb.dip0.t-ipconnect.de [217.91.15.219]) by pc3.berlin.powerweb.de (8.9.3p3/8.9.3) with ESMTP id MAA22349 for ; Thu, 22 Feb 2007 12:50:31 +0100 X-Delivered-To: Original-Received: (qmail 25081 invoked from network); 22 Feb 2007 11:50:33 -0000 Original-Received: from unknown (HELO lola.quinscape.zz) ([10.0.3.43]) (envelope-sender ) by ns.quinscape.de (qmail-ldap-1.03) with SMTP for ; 22 Feb 2007 11:50:33 -0000 Original-Received: by lola.quinscape.zz (Postfix, from userid 1001) id C429623889; Thu, 22 Feb 2007 12:50:33 +0100 (CET) In-Reply-To: (Kenichi Handa's message of "Thu\, 22 Feb 2007 20\:44\:23 +0900") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-detected-kernel: Linux 2.4-2.6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:66610 Archived-At: Kenichi Handa writes: > In article <877iuablng.fsf@pacem.orebokech.com>, Romain Francoise writes: > > (gdb) watch ((struct Lisp_Symbol *) 0x838c8f8)->value > Hardware watchpoint 4: ((struct Lisp_Symbol *) 137939192)->value > (gdb) c > Continuing. > > then, did this in Emacs: > > M-x byte-compile-file RET ~/Fontifier.el RET > > then, Emacs stopped as below: > > Hardware watchpoint 4: ((struct Lisp_Symbol *) 137939192)->value > > Old value = 137939193 > New value = 144315101 > print_preprocess (obj=144315101) at print.c:1415 > (gdb) > > The lines around print.c:1415 are: > > 1412 /* If Vprint_continuous_numbering is non-nil and OBJ is a gensym, > 1413 always print the gensym with a number. This is a special for > 1414 the lisp function byte-compile-output-docform. */ > 1415 if (!NILP (Vprint_continuous_numbering) > 1416 && SYMBOLP (obj) > 1417 && !SYMBOL_INTERNED_P (obj)) > 1418 PRINT_NUMBER_STATUS (Vprint_number_table, print_number_index) = Qt; > 1419 print_number_index++; > > I have no idea why the value of Qt is changed at L1415 (note > that I compiled print.c without optimization). Well, you'll get pointed to the IP after the hardware breakpoint triggered. So the interesting code would be before those comments. -- David Kastrup