Remove obsolete SETUP_ARBITRARY_FRAME references

[Fred Fish <fnf@specifix.com>]

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  <fnf@specifix.com>
 
 	* stack.c (parse_frame_specification_1): Remove use of obsolete
 	SETUP_ARBITRARY_FRAME macro.

Entry for doc/ChangeLog:

	2005-08-01  Fred Fish  <fnf@specifix.com>

	* 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 ----