This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Should there be a gdb_test_backtrace?

From: Andrew Cagney <cagney at gnu dot org>
To: Michael Elizabeth Chastain <mec dot gnu at mindspring dot com>
Cc: gdb at sources dot redhat dot com, randolph at tausq dot org
Date: Thu, 15 Jul 2004 14:45:41 -0400
Subject: Re: Should there be a gdb_test_backtrace?
References: <20040712183056.A486D4B104@berman.michael-chastain.com>

I think gdb_test_backtrace would be an interesting idea.
Also, it could implement an output limit.  Sometimes
gdb goes into an infinite backtrace and it would be nice
if gdb_test_backtrace gave a special FAIL when it saw
stack frame #1000 and killed gdb.

Supplemental question :-) Should there be a gdb_test_list to go with / supersede gdb_expect_list?

Andrew

References:
- Re: Should there be a gdb_test_backtrace?
  - From: Michael Elizabeth Chastain

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]