From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13536 invoked by alias); 25 May 2009 20:59:25 -0000 Received: (qmail 13527 invoked by uid 22791); 25 May 2009 20:59:25 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout4.012.net.il (HELO mtaout3.012.net.il) (84.95.2.10) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 25 May 2009 20:59:18 +0000 Received: from conversion-daemon.i_mtaout3.012.net.il by i_mtaout3.012.net.il (HyperSendmail v2004.12) id <0KK700C00WO5Y700@i_mtaout3.012.net.il> for gdb-patches@sourceware.org; Mon, 25 May 2009 23:59:16 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.228.115.215]) by i_mtaout3.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KK700FYPWYMPO10@i_mtaout3.012.net.il>; Mon, 25 May 2009 23:59:16 +0300 (IDT) Date: Mon, 25 May 2009 20:59:00 -0000 From: Eli Zaretskii Subject: Re: [rfc] Remove current_gdbarch register handling from symbol readers In-reply-to: <200905251314.n4PDEdWQ015511@d12av02.megacenter.de.ibm.com> To: Ulrich Weigand Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83skissxuo.fsf@gnu.org> References: <200905251314.n4PDEdWQ015511@d12av02.megacenter.de.ibm.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-05/txt/msg00568.txt.bz2 > Date: Mon, 25 May 2009 15:14:39 +0200 (CEST) > From: "Ulrich Weigand" > Cc: gdb-patches@sourceware.org > > So overall it seems that *no* target uses COFF/SDB debug info as its > default format any more; those that still support it at all also use > a more powerful format as default. Under those circumstances, is there > any benefit to continuing to support that format in GDB, given that it > becomes more and more diffcult to test that this support actually > still works? DJGPP needs support for the COFF debug info because the DJGPP port of Emacs can only be built with -gcoff. That's because no one ported unexec.c in Emacs to DWARF-2 debug info embedded in COFF binary format. I don't expect such changes in unexec.c any time soon. > > The problem is that DJGPP does not support expect, so the the test > > suite cannot be run. I can run some tests manually, so if you or > > someone else could tell which test may be affected by this change, I > > can try running them. > > Pretty much any access to an in-register local variable or parameter > should break if the change is wrong. OK, I will run at least some of them.