From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"Wiederhake, Tim" <tim.wiederhake@intel.com>,
"xdje42@gmail.com" <xdje42@gmail.com>,
Joel Brobecker <brobecker@adacore.com>
Subject: RE: GDB 8.0 release/branching 2017-03-20 update
Date: Wed, 29 Mar 2017 06:08:00 -0000 [thread overview]
Message-ID: <A78C989F6D9628469189715575E55B2340076209@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <86a885o0z2.fsf@gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2337 bytes --]
Hello Yao,
> >> struct PyGetSetDef py_insn_getset[] =
> >> {
> >> { "data", py_insn_data, NULL, "raw instruction data", NULL},
> >> { "decoded", py_insn_decode, NULL, "decoded instruction", NULL},
> >> { "size", py_insn_size, NULL, "instruction size in byte", NULL},
> >> { "pc", py_insn_pc, NULL, "instruction address", NULL },
> >> {NULL}
> >> };
> >
> > This is for the (abstract) base-class, I assume.
> >
>
> Yes, it is the base class, but it is the implementation detail about the
> class is abstract or not. I haven't think about it yet. Again, I only
> care about python interface at this stage.
>
> > We don't store any data in the base class so the Python object would
> > contain the PyObject header and nothing else, correct?
> >
> > And the above functions would throw an exception or return None.
> > Correct?
> >
>
> I didn't go that far yet :)
What else could the do? We agreed that the base class will be abstract and
let the derived classes chose the data members to best implement the functions.
> >> struct PyGetSetDef btpy_insn_getset[] =
> >> {
> >> { "data", btpy_insn_data, NULL, "raw instruction data", NULL},
> >> { "decoded", btpy_insn_decode, NULL, "decoded instruction", NULL},
> >> { "size", btpy_insn_size, NULL, "instruction size in byte", NULL},
> >> { "pc", btpy_insn_pc, NULL, "instruction address", NULL },
> >>
> >> { "number", btpy_number, NULL, "instruction number", NULL},
> >> { "sal", btpy_sal, NULL, "instruction number", NULL},
> >> {NULL}
> >> };
> >
> > This is for the BtraceInstruction derived class, I assume. That's essentially
> > what Tim implemented. Correct?
> >
> > This doesn't look too far away from what we have in GDB today.
>
> I requested to change the python interface in Tim's patch, not the
> implementation.
Now I'm a bit lost. What exactly do you want changed at this point to
establish the Python interface?
Thanks,
Markus.
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
\x16º&Öéj×!zÊÞ¶êç×~üç©b²Ö«r\x18\x1dnr\x17¬
next prev parent reply other threads:[~2017-03-29 6:08 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 20:16 Joel Brobecker
2017-03-20 20:21 ` Keith Seitz
2017-03-20 22:39 ` Yao Qi
2017-03-20 22:47 ` Yao Qi
2017-03-20 22:52 ` Joel Brobecker
2017-03-20 23:03 ` Yao Qi
2017-03-21 13:28 ` Joel Brobecker
2017-03-21 7:35 ` Wiederhake, Tim
2017-03-21 13:28 ` Joel Brobecker
2017-03-21 13:07 ` Yao Qi
2017-03-21 13:31 ` Joel Brobecker
2017-03-22 13:58 ` Metzger, Markus T
2017-03-22 17:09 ` Yao Qi
2017-03-23 16:01 ` Metzger, Markus T
2017-03-23 17:25 ` Yao Qi
2017-03-23 18:17 ` Metzger, Markus T
2017-03-24 14:41 ` Yao Qi
2017-03-27 10:51 ` Metzger, Markus T
2017-03-27 11:19 ` Yao Qi
2017-03-27 12:46 ` Metzger, Markus T
2017-03-27 16:03 ` Yao Qi
2017-03-28 7:16 ` Metzger, Markus T
2017-03-28 13:25 ` Yao Qi
2017-03-28 15:08 ` Metzger, Markus T
2017-03-28 15:49 ` Yao Qi
2017-03-29 6:08 ` Metzger, Markus T [this message]
[not found] ` <861stgo072.fsf@gmail.com>
2017-03-29 14:38 ` Metzger, Markus T
2017-03-30 10:50 ` Yao Qi
2017-03-30 11:58 ` Metzger, Markus T
[not found] ` <86h92a4w86.fsf@gmail.com>
2017-03-30 15:55 ` Metzger, Markus T
2017-03-31 13:55 ` Yao Qi
2017-03-31 15:21 ` Metzger, Markus T
2017-03-31 16:02 ` Joel Brobecker
2017-04-06 14:40 ` Wiederhake, Tim
2017-04-07 8:10 ` Yao Qi
2017-04-07 11:53 ` Wiederhake, Tim
2017-04-07 15:19 ` Yao Qi
2017-03-21 14:00 ` Yao Qi
2017-03-21 14:03 ` Pedro Alves
2017-03-27 13:35 ` Antoine Tremblay
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=A78C989F6D9628469189715575E55B2340076209@IRSMSX104.ger.corp.intel.com \
--to=markus.t.metzger@intel.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.com \
--cc=tim.wiederhake@intel.com \
--cc=xdje42@gmail.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