From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4827 invoked by alias); 25 Jan 2009 01:17:17 -0000 Received: (qmail 4818 invoked by uid 22791); 25 Jan 2009 01:17:16 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.23) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 25 Jan 2009 01:17:12 +0000 Received: from kahikatea.snap.net.nz (unknown [123.255.31.195]) by viper.snap.net.nz (Postfix) with ESMTP id 569B23DA710; Sun, 25 Jan 2009 14:17:10 +1300 (NZDT) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id 355208FC6D; Sun, 25 Jan 2009 14:17:03 +1300 (NZDT) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18811.48525.730689.724019@kahikatea.snap.net.nz> Date: Sun, 25 Jan 2009 01:17:00 -0000 To: "Dave Milter" Cc: "Andreas Schwab" , gdb@sourceware.org Subject: Re: emacs and gdb In-Reply-To: <2a382c6e0811060231n58f95a98u375068098d818ba7@mail.gmail.com> References: <2a382c6e0811052307r6ae0510ewf5569f59c93446a6@mail.gmail.com> <2a382c6e0811060139t324eb182h11400093efa65af5@mail.gmail.com> <2a382c6e0811060231n58f95a98u375068098d818ba7@mail.gmail.com> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-01/txt/msg00166.txt.bz2 > (gdb) target remote :3333 > Remote debugging using :3333 > 0x00000004 in ?? () > (gdb) info frame > Cannot access memory at address 0xffe7fdff > Stack level 0, frame at 0x0: > pc = 0x4; saved pc > /home/test/src/toolchains/gdb/gdb-6.8.50.20080706/gdb/findvar.c:298: > internal-error: value_of_register_lazy: Assertion `frame_id_p > (get_frame_id (frame))' failed. > A problem internal to GDB has been detected, > further debugging may prove unreliable. > > emacs call info frame, and this cause gdb failure, > is this gdb bug? Yes, I think this is a gdb bug and I have filed a bug report here: http://sourceware.org/bugzilla/show_bug.cgi?id=9786 -- Nick http://www.inet.net.nz/~nickrob