OK.  this is in partial responce to:
	http://sourceware.org/ml/gdb-patches/2005-04/msg00145.html

This patch adds a new test file, setbacktrace.exp along with a new 'c' test program,
setbacktrace.c.

The purpose of this new test is to check backtrace releated features not tested
elsewhere in the testsuit:
   *  Check that we know what backtrace options are available.
   *  Check that GDB will only backtrace the requested number of frames.
   *  Check that GDB doesn't backtrace past main unless asked to do so.

One problem:  I don't know how to add new files in a patch.  So I have attached the files
and include only the ChangeLog entry here in the body of this e-mail.

-=# Paul #=-

2005-04-15   Paul Gililam  <pgilliam@us.ibm.com>

	* gdb.base/setbacktrace.exp (new file): Check backtrace releated
        features not tested elsewhere.
        * gdb.base/setbacktrace.c (new file): Test case used by above.