From: "Willgerodt, Felix" <felix.willgerodt@intel.com>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH v5 09/10] btrace, python: Enable ptwrite filter registration.
Date: Tue, 26 Jul 2022 14:08:37 +0000 [thread overview]
Message-ID: <MN2PR11MB4566DF990F71585020DFCE4D8E949@MN2PR11MB4566.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DM8PR11MB57490EF5847C89B7B2F87BC4DE899@DM8PR11MB5749.namprd11.prod.outlook.com>
> -----Original Message-----
> From: Metzger, Markus T <markus.t.metzger@intel.com>
> Sent: Mittwoch, 13. Juli 2022 17:21
> To: Willgerodt, Felix <felix.willgerodt@intel.com>
> Cc: gdb-patches@sourceware.org
> Subject: RE: [PATCH v5 09/10] btrace, python: Enable ptwrite filter
> registration.
>
> Hello Felix,
>
> >I get your argumentation. I still think ptw_filter is perfectly fine. As that is
> >what it will always be, even for other extension languages. I see it more
> >from a "global GDB" perspective, rather than "btrace vs python" or from a
> >"callback concept" POV.
> >Regardless, I will call it to ptw_context in the next revision. Is that ok?
>
> That sounds OK. How about avoiding the problem by doing it with a C++
> callable?
I don't think I completely follow what you are proposing or what we would
gain. I guess I can make the callback_fun e.g. a std::function or a
callable class/struct. We will still need to save a pointer for the
ptw_context/filter in btinfo (or the callable class/struct member), as we pass
that to the Python C API. To me this doesn't avoid the naming problem.
>+ # Clean-up old filters.
> >+ for key in _ptwrite_filter.keys():
> >+ if key not in lwp_list and key != "global":
> >+ _ptwrite_filter.pop(key)
>
> We just cleared the filters. There are no existing filters.
Right.
> >+
> >+ # Register filter for new threads.
> >+ for key in lwp_list:
> >+ if key not in _ptwrite_filter.keys():
> >+ _ptwrite_filter[key] = deepcopy(_ptwrite_filter["global"])
>
> New filters are added on-demand below. I don't think this is necessary.
Right again. Thanks for the help, these two things make it much simpler.
> >
> >
> > def get_filter():
> > """Returns the filters of the current thread."""
> >- thread_list = gdb.Inferior.threads(gdb.selected_inferior())
> >- _update_filter_dict(thread_list)
> >+ key = gdb.selected_thread().ptid[1]
> >+
> >+ # This could be a new thread.
> >+ if key not in _ptwrite_filter.keys():
> >+ _ptwrite_filter[key] = deepcopy(_ptwrite_filter["global"])
> >
> >- return _ptwrite_filter[gdb.selected_thread().ptid[1]]
> >+ return _ptwrite_filter[key]
>
> That looks good.
>
> We're no longer pruning filters for exited threads. We could do so on
> inferior exit. Would that suffice?
Pruning on inferior exit only helps in certain cases.
We can't get a complete "all-past-threads" list from GDB for an exited
inferior though. And we can't just remove every dict entry except for
"global", as we could be debugging multiple inferiors.
What I could do is add e.g. the inferior id to the dict. And prune only these on
inferior exit:
+def ptw_exit_handler(event):
+ """Exit handler to prune _ptwrite_filter on inferior exit."""
+ for key in _ptwrite_filter.keys():
+ if key.startswith(f"{event.inferior.pid}."):
+ del _ptwrite_filter[key]
+
+
def _clear_traces(thread_list):
"""Helper function to clear the trace of all threads in THREAD_LIST."""
current_thread = gdb.selected_thread()
@@ -59,10 +66,13 @@ def register_filter(filter):
def get_filter():
"""Returns the filters of the current thread."""
- key = gdb.selected_thread().ptid[1]
+ key = f"{gdb.selected_inferior().pid}.{gdb.selected_thread().ptid[1]}"
# This could be a new thread.
if key not in _ptwrite_filter.keys():
_ptwrite_filter[key] = deepcopy(_ptwrite_filter["global"])
return _ptwrite_filter[key]
+
+
+gdb.events.exited.connect(ptw_exit_handler)
Regards,
Felix
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2022-07-26 14:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 11:43 [PATCH v5 00/10] Extensions for PTWRITE Felix Willgerodt
2022-06-22 11:43 ` [PATCH v5 01/10] btrace: Introduce auxiliary instructions Felix Willgerodt
2022-06-28 9:10 ` Metzger, Markus T
2022-06-22 11:43 ` [PATCH v5 02/10] btrace: Enable auxiliary instructions in record instruction-history Felix Willgerodt
2022-06-28 9:10 ` Metzger, Markus T
2022-06-28 11:28 ` Willgerodt, Felix
2022-06-29 10:43 ` Metzger, Markus T
2022-06-22 11:43 ` [PATCH v5 03/10] btrace: Enable auxiliary instructions in record function-call-history Felix Willgerodt
2022-06-28 9:10 ` Metzger, Markus T
2022-09-19 8:59 ` Willgerodt, Felix
2022-06-22 11:43 ` [PATCH v5 04/10] btrace: Handle stepping and goto for auxiliary instructions Felix Willgerodt
2022-06-28 9:11 ` Metzger, Markus T
2022-06-22 11:43 ` [PATCH v5 05/10] python: Introduce gdb.RecordAuxiliary class Felix Willgerodt
2022-06-28 9:11 ` Metzger, Markus T
2022-07-11 12:48 ` Willgerodt, Felix
2022-06-22 11:43 ` [PATCH v5 06/10] python: Add clear() to gdb.Record Felix Willgerodt
2022-06-28 9:11 ` Metzger, Markus T
2022-06-22 11:43 ` [PATCH v5 07/10] btrace, gdbserver: Add ptwrite to btrace_config_pt Felix Willgerodt
2022-06-28 9:11 ` Metzger, Markus T
2022-06-22 11:43 ` [PATCH v5 08/10] btrace, linux: Enable ptwrite packets Felix Willgerodt
2022-06-28 9:12 ` Metzger, Markus T
2022-06-22 11:43 ` [PATCH v5 09/10] btrace, python: Enable ptwrite filter registration Felix Willgerodt
2022-06-28 13:59 ` Metzger, Markus T
2022-07-11 12:48 ` Willgerodt, Felix
2022-07-12 12:23 ` Metzger, Markus T
2022-07-13 8:49 ` Willgerodt, Felix
2022-07-13 15:20 ` Metzger, Markus T
2022-07-26 14:08 ` Willgerodt, Felix [this message]
2022-09-14 8:37 ` Metzger, Markus T
2022-06-22 11:43 ` [PATCH v5 10/10] btrace: Extend ptwrite event decoding Felix Willgerodt
2022-06-29 13:35 ` Metzger, Markus T
2022-09-19 8:59 ` Willgerodt, Felix
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=MN2PR11MB4566DF990F71585020DFCE4D8E949@MN2PR11MB4566.namprd11.prod.outlook.com \
--to=felix.willgerodt@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).