This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Testsuite failure in gdb.cp/annota2.exp
- From: Nick Roberts <nickrob at snap dot net dot nz>
- To: Andreas Schwab <schwab at suse dot de>
- Cc: gdb-patches at sourceware dot org
- Date: Sat, 27 Jan 2007 11:02:11 +1300
- Subject: Re: Testsuite failure in gdb.cp/annota2.exp
- References: <jer6thddgf.fsf@sykes.suse.de>
> The test "watch triggered on a.x" fails on ia64 because it only allows 3
> or 4 occurences of "frames-invalid", but I get 6 of them. What is the
> significance of the "frames-invalid" annotation?
I think the idea was that a frontend need only recompute the call stack when a
"frames-invalid" annotation was issued. The problem is that almost any
activity seems to generate at least one, and frequently large numbers of such
annotations (they get printed every time flush_cached_frames is called).
Incidentally this test and the other don't pass on GNU/Linux either but the
fails are masked by PR gdb/38.
--
Nick http://www.inet.net.nz/~nickrob