Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Aktemur, Tankut Baris via Gdb-patches" <gdb-patches@sourceware.org>
To: "Strasuns, Mihails" <mihails.strasuns@intel.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH] gdb: get jiter objfile from a bound minsym
Date: Mon, 19 Oct 2020 10:39:59 +0000	[thread overview]
Message-ID: <SN6PR11MB28931964EC65C883CF18F002C41E0@SN6PR11MB2893.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20201019094943.GA28735@embecosm.com>

Hi Mihails,

A few nits below.

On Monday, October 19, 2020 11:50 AM, Andrew Burgess wrote:
> * Mihails Strasuns via Gdb-patches <gdb-patches@sourceware.org> [2020-10-14 11:00:03 +0200]:
> 
> > This fixes a regression introduced by the following commit:
> >
> > fe053b9e853 gdb/jit: pass the jiter objfile as an argument to jit_event_handler
> >
> > In the refactoring `handle_jit_event` function was changed to pass a matching
> > objfile pointer to the `jit_event_handler` explicitly, rather using internal
> > storage:
> >
> > ```
> > --- a/gdb/breakpoint.c
> > +++ b/gdb/breakpoint.c
> > @@ -5448,8 +5448,9 @@ handle_jit_event (void)
> >
> >    frame = get_current_frame ();
> >    gdbarch = get_frame_arch (frame);
> > +  objfile *jiter = symbol_objfile (get_frame_function (frame));
> >
> > -  jit_event_handler (gdbarch);
> > +  jit_event_handler (gdbarch, jiter);
> > ```
> >
> > This was needed to add support for a multiple jiters in a following commits.

"a multiple jiters" -> "multiple jiters"
"in a following commits" -> "in a subsequent commit."? Or maybe just end the
sentence after "jiters".

> > However it has also introduced a regression, because `get_frame_function
> > (frame)` here may return `nullptr`, resulting in a crash.
> >
> > A more resilient way would be to use an approach mirroring
> > `jit_breakpoint_re_set` - to find a minimal symbol matching the breakpoint
> > location and use its object file. We know that this breakpoint events comes

Dot-space-space.
"events" -> "event"

> > from a breakpoint set by `jit_breakpoint_re_set`, thus using the reverse
> > approach should be reliable enough.
> >
> > gdb/Changelog:
> > 2020-10-14  Mihails Strasuns  <mihails.strasuns@intel.com>
> >
> > 	* breakpoint.c (handle_jit_event): and an argument, change how

"and" -> "Add"

Thanks for the fix.  It makes sense to me.

-Baris


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, Gary Kershaw
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

  reply	other threads:[~2020-10-19 10:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14  9:00 Mihails Strasuns via Gdb-patches
2020-10-14  9:01 ` Strasuns, Mihails via Gdb-patches
2020-10-19  9:49 ` Andrew Burgess
2020-10-19 10:39   ` Aktemur, Tankut Baris via Gdb-patches [this message]
2020-10-19 14:58     ` Strasuns, Mihails via Gdb-patches

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=SN6PR11MB28931964EC65C883CF18F002C41E0@SN6PR11MB2893.namprd11.prod.outlook.com \
    --to=gdb-patches@sourceware.org \
    --cc=mihails.strasuns@intel.com \
    --cc=tankut.baris.aktemur@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