From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4318 invoked by alias); 1 Aug 2005 17:40:22 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 4309 invoked by uid 22791); 1 Aug 2005 17:40:18 -0000 Received: from w099.z064220152.sjc-ca.dsl.cnc.net (HELO duck.specifix.com) (64.220.152.99) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 01 Aug 2005 17:40:18 +0000 Received: from diveadx (duck.specifix.com [64.220.152.99]) by duck.specifix.com (Postfix) with ESMTP id B60EF4029; Mon, 1 Aug 2005 10:40:15 -0700 (PDT) From: Fred Fish Reply-To: fnf@specifix.com To: gdb-patches@sources.redhat.com Subject: Remove obsolete SETUP_ARBITRARY_FRAME references Date: Mon, 01 Aug 2005 17:40:00 -0000 User-Agent: KMail/1.8.2 Cc: fnf@specifix.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508011340.10465.fnf@specifix.com> X-SW-Source: 2005-08/txt/msg00022.txt.bz2 This change removes the last references to the obsolete SETUP_ARBITRARY_FRAME macro. OK to apply? -Fred ============================================================================ Entry for ChangeLog: 2005-08-01 Fred Fish * stack.c (parse_frame_specification_1): Remove use of obsolete SETUP_ARBITRARY_FRAME macro. Entry for doc/ChangeLog: 2005-08-01 Fred Fish * gdb.texinfo (SETUP_ARBITRARY_FRAME): Remove obsolete reference. Index: stack.c =================================================================== RCS file: /cvs/src/src/gdb/stack.c,v retrieving revision 1.133 diff -c -p -r1.133 stack.c *** stack.c 22 May 2005 14:53:34 -0000 1.133 --- stack.c 1 Aug 2005 17:35:14 -0000 *************** parse_frame_specification_1 (const char *** 817,838 **** struct frame_id id = frame_id_build_wild (addrs[0]); struct frame_info *fid; - /* If SETUP_ARBITRARY_FRAME is defined, then frame - specifications take at least 2 addresses. It is important to - detect this case here so that "frame 100" does not give a - confusing error message like "frame specification requires - two addresses". This of course does not solve the "frame - 100" problem for machines on which a frame specification can - be made with one address. To solve that, we need a new - syntax for a specifying a frame by address. I think the - cleanest syntax is $frame(0x45) ($frame(0x23,0x45) for two - args, etc.), but people might think that is too much typing, - so I guess *0x23,0x45 would be a possible alternative (commas - really should be used instead of spaces to delimit; using - spaces normally works in an expression). */ - #ifdef SETUP_ARBITRARY_FRAME - error (_("No frame %s"), paddr_d (addrs[0])); - #endif /* If (s)he specifies the frame with an address, he deserves what (s)he gets. Still, give the highest one that matches. (NOTE: cagney/2004-10-29: Why highest, or outer-most, I don't --- 817,822 ---- Index: doc/gdb.texinfo =================================================================== RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v retrieving revision 1.275 diff -c -p -r1.275 gdb.texinfo *** doc/gdb.texinfo 15 Jul 2005 05:58:17 -0000 1.275 --- doc/gdb.texinfo 1 Aug 2005 17:35:19 -0000 *************** pointer and a program counter. *** 4399,4407 **** On the 29k architecture, it needs three addresses: a register stack pointer, a program counter, and a memory stack pointer. - @c note to future updaters: this is conditioned on a flag - @c SETUP_ARBITRARY_FRAME in the tm-*.h files. The above is up to date - @c as of 27 Jan 1994. @kindex up @item up @var{n} --- 4399,4404 ----