public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@arm.com>
To: Enze Li <enze.li@hotmail.com>, gdb-patches@sourceware.org
Cc: enze.li@gmx.com, jhb@FreeBSD.org
Subject: Re: [PATCH v2] gdb/hurd: pass memory_tagged as false to find_memory_region_ftype
Date: Mon, 25 Jul 2022 08:39:51 +0100	[thread overview]
Message-ID: <6ec77420-8123-676c-ebba-20d55a5222fd@arm.com> (raw)
In-Reply-To: <OS3P286MB21525F30AEDA0EE2EEC86D27F0929@OS3P286MB2152.JPNP286.PROD.OUTLOOK.COM>

Hi!

On 7/24/22 04:40, Enze Li wrote:
> I tried building GDB on GNU/Hurd, and ran into this error:
> 
>    CXX    gnu-nat.o
> gnu-nat.c: In member function ‘virtual int gnu_nat_target::find_memory_regions(find_memory_region_ftype, void*)’:
> gnu-nat.c:2620:21: error: too few arguments to function
>   2620 |             (*func) (last_region_address,
>        |             ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~
>   2621 |                      last_region_end - last_region_address,
>        |                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   2622 |                      last_protection & VM_PROT_READ,
>        |                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   2623 |                      last_protection & VM_PROT_WRITE,
>        |                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   2624 |                      last_protection & VM_PROT_EXECUTE,
>        |                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   2625 |                      1, /* MODIFIED is unknown, pass it as true.  */
>        |                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   2626 |                      data);
>        |                      ~~~~~
> gnu-nat.c:2635:13: error: too few arguments to function
>   2635 |     (*func) (last_region_address, last_region_end - last_region_address,
>        |     ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   2636 |              last_protection & VM_PROT_READ,
>        |              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   2637 |              last_protection & VM_PROT_WRITE,
>        |              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   2638 |              last_protection & VM_PROT_EXECUTE,
>        |              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   2639 |              1, /* MODIFIED is unknown, pass it as true.  */
>        |              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   2640 |              data);
>        |              ~~~~~
> make[2]: *** [Makefile:1926: gnu-nat.o] Error 1
> 
> This is because in this commit:
> 
>    commit 68cffbbd4406b4efe1aa6e18460b1d7ca02549f1
>    Date:   Thu Mar 31 11:42:35 2022 +0100
> 
>        [AArch64] MTE corefile support
> 
> Added a new argument to find_memory_region_ftype, but did not pass it to
> the function in gnu-nat.c.  Fix this by passing memory_tagged as false.
> 
> As Luis pointed out, similar bugs may also appear on FreeBSD and NetBSD,
> and I have reproduced them on both systems.  This patch fixes them
> incidentally.
> 
> Tested by rebuilding on GNU/Hurd, FreeBSD/amd64 and NetBSD/amd64.
> ---
>   gdb/fbsd-nat.c   | 2 +-
>   gdb/gnu-nat.c    | 2 ++
>   gdb/netbsd-nat.c | 2 +-
>   3 files changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/gdb/fbsd-nat.c b/gdb/fbsd-nat.c
> index 398f1c18b33..a4ca4a53415 100644
> --- a/gdb/fbsd-nat.c
> +++ b/gdb/fbsd-nat.c
> @@ -125,7 +125,7 @@ fbsd_nat_target::find_memory_regions (find_memory_region_ftype func,
>   	 Pass MODIFIED as true, we do not know the real modification state.  */
>         func (kve->kve_start, size, kve->kve_protection & KVME_PROT_READ,
>   	    kve->kve_protection & KVME_PROT_WRITE,
> -	    kve->kve_protection & KVME_PROT_EXEC, 1, data);
> +	    kve->kve_protection & KVME_PROT_EXEC, 1, false, data);
>       }
>     return 0;
>   }
> diff --git a/gdb/gnu-nat.c b/gdb/gnu-nat.c
> index 72314824278..5dd4d148c76 100644
> --- a/gdb/gnu-nat.c
> +++ b/gdb/gnu-nat.c
> @@ -2623,6 +2623,7 @@ gnu_nat_target::find_memory_regions (find_memory_region_ftype func,
>   		     last_protection & VM_PROT_WRITE,
>   		     last_protection & VM_PROT_EXECUTE,
>   		     1, /* MODIFIED is unknown, pass it as true.  */
> +		     false, /* No memory tags in the object file.  */
>   		     data);
>   	  last_region_address = region_address;
>   	  last_region_end = region_address += region_length;
> @@ -2637,6 +2638,7 @@ gnu_nat_target::find_memory_regions (find_memory_region_ftype func,
>   	     last_protection & VM_PROT_WRITE,
>   	     last_protection & VM_PROT_EXECUTE,
>   	     1, /* MODIFIED is unknown, pass it as true.  */
> +	     false, /* No memory tags in the object file.  */
>   	     data);
>   
>     return 0;
> diff --git a/gdb/netbsd-nat.c b/gdb/netbsd-nat.c
> index c45df391afc..d3bf83d35f5 100644
> --- a/gdb/netbsd-nat.c
> +++ b/gdb/netbsd-nat.c
> @@ -259,7 +259,7 @@ nbsd_nat_target::find_memory_regions (find_memory_region_ftype func,
>   	 Pass MODIFIED as true, we do not know the real modification state.  */
>         func (kve->kve_start, size, kve->kve_protection & KVME_PROT_READ,
>   	    kve->kve_protection & KVME_PROT_WRITE,
> -	    kve->kve_protection & KVME_PROT_EXEC, 1, data);
> +	    kve->kve_protection & KVME_PROT_EXEC, 1, false, data);
>       }
>     return 0;
>   }

The above LGTM. Thanks again for getting these files fixed. I think this one can go in as it is
fairly obvious and addresses broken builds for hurd, fbsd and netbsd

  reply	other threads:[~2022-07-25  7:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22 14:11 [PATCH] " Enze Li
2022-07-22 14:47 ` Luis Machado
2022-07-24  3:59   ` Enze Li
2022-07-24  3:40 ` [PATCH v2] " Enze Li
2022-07-25  7:39   ` Luis Machado [this message]
2022-07-25 15:55     ` John Baldwin
2022-07-26 12:35       ` Enze Li

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=6ec77420-8123-676c-ebba-20d55a5222fd@arm.com \
    --to=luis.machado@arm.com \
    --cc=enze.li@gmx.com \
    --cc=enze.li@hotmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jhb@FreeBSD.org \
    /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).