This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [PATCH] add new .exp file and a 'c' testfile to test backtrace limits etc.
- From: Daniel Jacobowitz <drow at false dot org>
- To: Paul Gilliam <pgilliam at us dot ibm dot com>, gdb-patches at sources dot redhat dot com
- Date: Sat, 28 May 2005 18:55:43 -0400
- Subject: Re: [PATCH] add new .exp file and a 'c' testfile to test backtrace limits etc.
- References: <200504071025.11668.pgilliam@us.ibm.com> <20050414193642.GB19792@nevyn.them.org> <200504151602.39257.pgilliam@us.ibm.com> <20050430184914.GC7009@nevyn.them.org>
Hi Paul,
On Sat, Apr 30, 2005 at 02:49:14PM -0400, Daniel Jacobowitz wrote:
> On Fri, Apr 15, 2005 at 03:02:39PM -0800, Paul Gilliam wrote:
> > 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.
I sent you some comments on this patch in April. Here's another one
that may be useful:
http://sourceware.org/ml/gdb-patches/2005-05/msg00590.html
This patch fixed the bug I originally wanted this test case to test
for, and a couple of related bugs. If you don't have time, let me
know, and I'll try to update the test myself.
--
Daniel Jacobowitz
CodeSourcery, LLC