Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: "Agovic, Sanimir" <sanimir.agovic@intel.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFC 2/3] Perf test framework
Date: Tue, 03 Sep 2013 01:45:00 -0000	[thread overview]
Message-ID: <52253EFD.6040505@codesourcery.com> (raw)
In-Reply-To: <0377C58828D86C4588AEEC42FC3B85A71765866D@IRSMSX105.ger.corp.intel.com>

Sanimir,
Thanks for the review.

On 08/28/2013 05:57 PM, Agovic, Sanimir wrote:
> I would put a copyright header and a module __doc__ into __init__.py
>

What do you mean by "put a module __doc__ into __init__.py"?

>> >diff --git a/gdb/testsuite/gdb.perf/lib/perftest/perftest.py
>> >b/gdb/testsuite/gdb.perf/lib/perftest/perftest.py
>> >new file mode 100644
>> >index 0000000..b15fd39
>> >--- /dev/null
>> >+++ b/gdb/testsuite/gdb.perf/lib/perftest/perftest.py
>> >@@ -0,0 +1,49 @@
> [...]
>> >+
>> >+class TestCase(gdb.Function):
>> >+    """Base class of all performance testing cases.  It registers a GDB
>> >+    convenience function 'perftest'.  Invoke this convenience function
>> >+    in GDB will call method 'invoke'."""
>> >+
>> >+    def __init__(self, result):
>> >+        # Each test case registers a convenience function 'perftest'.
>> >+        super (TestCase, self).__init__ ("perftest")
>> >+        self.result = result
>> >+
>> >+    def execute_test(self):
>> >+        """Abstract method  to do the actual tests."""
>> >+        raise RuntimeError("Abstract Method.")
>> >
> You may use module abc instead:
> | class TestCase(gdb.Function):
> |  __metaclass__ = abc.ABCMeta
> |  @abc.abstractmethod
> |  def execute_test(self): pass
>
> Instantiating TestCase and subclasses without overriding execute_test will fail.
>

Abstract Base Class should be useful here.  It was introduced in python
2.6, but GDB should support some older pythons.  I don't know what are 
the versions of python GDB support, 2.4 ~ 3.0?, but some code in 
gdb/python/ is written with 2.4 considered.

Other comments are addressed, and I'll post the updated patch in next
round.

-- 
Yao (齐尧)


  reply	other threads:[~2013-09-03  1:45 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14 13:01 [RFC] GDB performance testing infrastructure Yao Qi
2013-08-21 20:39 ` Tom Tromey
2013-08-27  6:21   ` Yao Qi
2013-08-27 13:49 ` Agovic, Sanimir
2013-08-28  3:04   ` Yao Qi
2013-09-19  0:36     ` Doug Evans
2013-08-28  4:17 ` [RFC 0/3] GDB Performance testing Yao Qi
2013-08-28  4:17   ` [RFC 2/3] Perf test framework Yao Qi
2013-08-28  9:57     ` Agovic, Sanimir
2013-09-03  1:45       ` Yao Qi [this message]
2013-09-03  6:38         ` Agovic, Sanimir
2013-09-19 19:09     ` Doug Evans
2013-09-20  8:04       ` Yao Qi
2013-09-20 16:51         ` Doug Evans
2013-09-22  2:54           ` Yao Qi
2013-09-22 23:14             ` Doug Evans
2013-09-20 17:12         ` Doug Evans
2013-08-28  4:17   ` [RFC 1/3] New make target 'check-perf' and new dir gdb.perf Yao Qi
2013-08-28  9:40     ` Agovic, Sanimir
2013-09-19 17:47     ` Doug Evans
2013-09-20 19:00       ` Tom Tromey
2013-09-20 18:59     ` Tom Tromey
2013-08-28  4:17   ` [RFC 3/3] Test on solib load and unload Yao Qi
2013-08-28  4:27     ` Yao Qi
2013-08-28 11:31       ` Agovic, Sanimir
2013-09-03  1:59         ` Yao Qi
2013-09-03  6:33           ` Agovic, Sanimir
2013-09-02 15:24       ` Blanc, Nicolas
2013-09-03  2:04         ` Yao Qi
2013-09-03  7:50           ` Blanc, Nicolas
2013-09-19 22:45       ` Doug Evans
2013-09-20 19:19         ` Tom Tromey
2013-10-05  0:34           ` Doug Evans
2013-10-07 16:31             ` Tom Tromey
2013-09-22  6:25         ` Yao Qi
2013-09-23  0:14           ` Doug Evans
2013-09-24  2:31             ` Yao Qi
2013-10-05  0:37               ` Doug Evans
2013-09-20 19:14       ` Tom Tromey
2013-09-19 17:25   ` [RFC 0/3] GDB Performance testing Doug Evans

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52253EFD.6040505@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sanimir.agovic@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox