public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Simon Marchi (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: Mihails Strasuns <mihails.strasuns@intel.com>,
	gdb-patches@sourceware.org
Subject: [review] jit: minor improvement to debug logging
Date: Mon, 25 Nov 2019 14:06:00 -0000	[thread overview]
Message-ID: <20191125140636.0FCD420AF6@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1574686491000.Ie66064f3aaa1c74facfc025c8d87f3a057869779@gnutoolchain-gerrit.osci.io>

Simon Marchi has posted comments on this change.

Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/703
......................................................................


Patch Set 1:

(1 comment)

Hi Mihails,

Thanks for doing this, I just noted a small comment.

| --- gdb/jit.c
| +++ gdb/jit.c
| @@ -953,17 +953,19 @@ jit_register_code (struct gdbarch *gdbarch,
|  }
|  
|  /* This function unregisters JITed code and frees the corresponding
|     objfile.  */
|  
|  static void
|  jit_unregister_code (struct objfile *objfile)
|  {
| +  if (jit_debug)
| +    fprintf_unfiltered (gdb_stdlog, "jit_unregister_code (%p)\n", objfile);

PS1, Line 962:

For a reason I can't remember, we don't use %p (because it's not
reliable on some platform?).  Use "%s" with host_address_to_string
instead.

|    delete objfile;
|  }
|  
|  /* Look up the objfile with this code entry address.  */
|  
|  static struct objfile *
|  jit_find_objf_with_entry_addr (CORE_ADDR entry_addr)
|  {
|    for (objfile *objf : current_program_space->objfiles ())

-- 
Gerrit-Project: binutils-gdb
Gerrit-Branch: master
Gerrit-Change-Id: Ie66064f3aaa1c74facfc025c8d87f3a057869779
Gerrit-Change-Number: 703
Gerrit-PatchSet: 1
Gerrit-Owner: Mihails Strasuns <mihails.strasuns@intel.com>
Gerrit-CC: Simon Marchi <simon.marchi@polymtl.ca>
Gerrit-Comment-Date: Mon, 25 Nov 2019 14:06:35 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment

  reply	other threads:[~2019-11-25 14:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25 12:54 Mihails Strasuns (Code Review)
2019-11-25 14:06 ` Simon Marchi (Code Review) [this message]
2019-11-26 11:27 ` [review v2] " Mihails Strasuns (Code Review)
2019-11-26 11:28 ` Mihails Strasuns (Code Review)
2019-11-26 13:51 ` Tom Tromey (Code Review)
2019-11-27  1:08 ` Luis Machado (Code Review)
2019-11-28  8:48 ` [review v3] " Mihails Strasuns (Code Review)
2019-11-28  9:07 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-11-28  9:07 ` Sourceware to Gerrit sync (Code Review)

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=20191125140636.0FCD420AF6@gnutoolchain-gerrit.osci.io \
    --to=gerrit@gnutoolchain-gerrit.osci.io \
    --cc=gdb-patches@sourceware.org \
    --cc=gnutoolchain-gerrit@osci.io \
    --cc=mihails.strasuns@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).