This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v4 00/18] All-stop on top of non-stop
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Luis Machado <lgustavo at codesourcery dot com>
- Cc: Pedro Alves <palves at redhat dot com>, gdb-patches at sourceware dot org
- Date: Wed, 12 Aug 2015 13:55:56 -0700
- Subject: Re: [PATCH v4 00/18] All-stop on top of non-stop
- Authentication-results: sourceware.org; auth=none
- References: <1432250354-2721-1-git-send-email-palves at redhat dot com> <55C4E3BD dot 8040801 at redhat dot com> <20150812183208 dot GA24901 at adacore dot com> <55CBA0D1 dot 5000203 at codesourcery dot com> <20150812195948 dot GH22245 at adacore dot com> <55CBAA17 dot 4040605 at codesourcery dot com> <20150812203322 dot GB9183 at adacore dot com> <55CBAF3F dot 7070602 at codesourcery dot com>
> I was just pointing at the fact that we already have shared library tests,
> so those could be expanded to include this inter-dso call as opposed to
> having a different set of tests like your patch did. But you'd need to shape
> it in a way that exercises your amd64 failure mode then.
Ah, OK!
Speaking in general terms and for myself, I usually prefer to create new
testcases rather than piggy-back on existing ones, because I find it
simpler to do, and I also find it simpler to be certain that I'm not
altering the older testcases in a way that some tests are no longer
doing what they are supposed to do. And finally, it makes it easier to
investigate regressions, because the testcase is usually simpler that
way. Have you tried debugging a testcase where you have about 250 tests
before the failure, and you're not sure what's relevant and what is not?
;-)
--
Joel