This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC 2/2] Test entry values in trace frame
- From: Tom Tromey <tromey at redhat dot com>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: <gdb-patches at sourceware dot org>
- Date: Tue, 20 Aug 2013 11:48:47 -0600
- Subject: Re: [RFC 2/2] Test entry values in trace frame
- References: <1376379586-24150-1-git-send-email-yao at codesourcery dot com> <1376379586-24150-3-git-send-email-yao at codesourcery dot com>
>>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:
Yao> I don't emit a fail for it because I am not very sure it is expected
Yao> to be "unavailable". I am fine to kfail it.
Yao> I looked into a little, and looks reading entry value doesn't use
Yao> value availability-aware API. It is not an easy fix to me.
I think on the whole I'd rather we not check in a test that fails.
I know we already have tests like that, but what I've noticed is that
these tests only ever seem to be fixed as a side effect of fixing
something else. Otherwise the failures are just universally ignored.
I suppose the best thing to do is to file a bug about this problem.
Then you can attach this patch to the bug.
What do you think?
Tom