From: Luis Machado <luis.machado@arm.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix various procfs.c compilation errors
Date: Thu, 17 Nov 2022 10:08:23 +0000 [thread overview]
Message-ID: <dd1d1268-253c-ebf7-3086-e5984afa4957@arm.com> (raw)
In-Reply-To: <yddv8nd7vvw.fsf@CeBiTec.Uni-Bielefeld.DE>
On 11/17/22 09:50, Rainer Orth wrote:
> Hi Luis,
>
>>> * find_memory_regions_callback fails with
>>> /vol/src/gnu/gdb/hg/master/dist/gdb/procfs.c: In function ‘int
>>> find_memory_regions_callback(prmap*, find_memory_region_ftype, void*)’:
>>> /vol/src/gnu/gdb/hg/master/dist/gdb/procfs.c:3167:18: error: too few arguments to function
>>> 3167 | return (*func) ((CORE_ADDR) map->pr_vaddr,
>>> | ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> 3168 | map->pr_size,
>>> | ~~~~~~~~~~~~~
>>> 3169 | (map->pr_mflags & MA_READ) != 0,
>>> | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> 3170 | (map->pr_mflags & MA_WRITE) != 0,
>>> | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> 3171 | (map->pr_mflags & MA_EXEC) != 0,
>>> | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> 3172 | 1, /* MODIFIED is unknown, pass it as true. */
>>> | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> 3173 | data);
>>> | ~~~~~
>>> Again, procfs.c was overlooked when adding the new memory_tagged arg.
>>> Unfortunately, it wasn't even documented in gdb/defs.h when it was
>>> added in
>>>
>>
>> Sorry, that was an oversight. I failed to updated all the hooks. I think
>> there was a BSD one that got fixed after the following commit was pushed.
>
> no problem: the primary issue was finding/understanding what the new arg
> meant/needs to be here.
>
> Could you take care of updating the defs.h comment to avoid such
> confusion in the future?
Surely.
>
> Thanks.
> Rainer
>
prev parent reply other threads:[~2022-11-17 10:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 15:02 Rainer Orth
2022-11-16 15:53 ` Simon Marchi
2022-11-17 9:46 ` Rainer Orth
2022-11-16 17:30 ` Tom Tromey
2022-11-17 9:48 ` Rainer Orth
2022-11-16 19:04 ` Luis Machado
2022-11-17 9:50 ` Rainer Orth
2022-11-17 10:08 ` Luis Machado [this message]
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=dd1d1268-253c-ebf7-3086-e5984afa4957@arm.com \
--to=luis.machado@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).