From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [drew.adams@oracle.com: RE: weird defadvice bug with byte-compilation] Date: Thu, 15 Dec 2005 06:46:05 +0200 Message-ID: References: Reply-To: Eli Zaretskii NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1134622144 24176 80.91.229.2 (15 Dec 2005 04:49:04 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 15 Dec 2005 04:49:04 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Dec 15 05:49:01 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Eml1i-0005lX-0L for ged-emacs-devel@m.gmane.org; Thu, 15 Dec 2005 05:47:34 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Eml2K-0002Mk-1J for ged-emacs-devel@m.gmane.org; Wed, 14 Dec 2005 23:48:12 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Eml16-0001qb-4R for emacs-devel@gnu.org; Wed, 14 Dec 2005 23:46:56 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Eml13-0001p4-6f for emacs-devel@gnu.org; Wed, 14 Dec 2005 23:46:55 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Eml12-0001ow-Up for emacs-devel@gnu.org; Wed, 14 Dec 2005 23:46:53 -0500 Original-Received: from [192.114.186.66] (helo=romy.inter.net.il) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Eml3B-0007n6-6t; Wed, 14 Dec 2005 23:49:05 -0500 Original-Received: from HOME-C4E4A596F7 (IGLD-80-230-86-229.inter.net.il [80.230.86.229]) by romy.inter.net.il (MOS 3.7.2-GA) with ESMTP id DEK71974 (AUTH halo1); Thu, 15 Dec 2005 06:46:05 +0200 (IST) Original-To: rms@gnu.org In-reply-to: (rms@gnu.org) 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:47776 Archived-At: > From: "Richard M. Stallman" > CC: emacs-devel@gnu.org > Date: Wed, 14 Dec 2005 21:09:16 -0500 > > Unfortunately, I cannot show this in the C traceback, because GDB > chokes on the next stack frame: > > #39 0x0112ae03 in single_menu_item (key=28443961, item=0, > pending_maps_ptr=0x82d09c, notreal=0, maxdepth=9) at w32menu.c:522 > #40 0x0112b0ee in single_keymap_panes (keymap=28443961, pane_name=0, prefix=9, > notreal=17085537, maxdepth=24660221) at w32menu.c:468 > #41 0x00000000 in ?? () from > #42 0x00000009 in ?? () > #43 0x0104b461 in parse_menu_item (item=480, notreal=8573128, > inmenubar=18001130) at keyboard.c:7376 > #44 0x01c76008 in ?? () > #45 0x000001e0 in ?? () > #46 0x0082d0c8 in ?? () > #47 0x0112acea in grow_menu_items () at w32menu.c:329 > #48 0x01011575 in x_y_to_hpos_vpos (w=0x1b20539, x=Cannot access memory at address 0x1b016c00) at xdisp.c:1005 > Cannot access memory at address 0x1b016c14 > > This means the stack is corrupted. We need to find out why and how, > because that could be the most important bug. No, the stack is not corrupted. The problem is that latest versions of GDB modified their way of analyzing function prologues, and that caused major regressions in stack backtraces on x86, especially with latest versions of GCC. That has been discussed extensively on the GDB mailing list during the last year. GDB 6.4 is supposed to improve on that, but I don't yet have its Windows port.