From: Simon Marchi <simark@simark.ca>
To: Kamil Rytarowski <n54@gmx.com>, gdb-patches@sourceware.org
Cc: tom@tromey.com
Subject: Re: [PATCH v4] Implement "info proc mappings" for NetBSD
Date: Sat, 11 Apr 2020 19:49:25 -0400 [thread overview]
Message-ID: <e027d897-8449-61c8-a715-47998e63e463@simark.ca> (raw)
In-Reply-To: <20200411234507.17070-1-n54@gmx.com>
On 2020-04-11 7:45 p.m., Kamil Rytarowski wrote:
> Define nbsd_nat_target::find_memory_regions and
> nbsd_nat_target::info_proc. info_proc handles as of now only
> the "mappings" command.
>
> Define a local static function kinfo_get_vmmap() that reads
> the process memory layout of a specified process.
> kinfo_get_vmmap() wraps the sysctl(3) call.
>
> nbsd-tdep.c defines now utility functions for printing the
> process memory layout:
> * nbsd_info_proc_mappings_header()
> * nbsd_vm_map_entry_flags()
> * nbsd_info_proc_mappings_entry()
When sending a new version, can you please rebase it on the current master?
The patch does not apply cleanly on master today, so it doesn't really reflect what's
going to be merged.
Simon
next prev parent reply other threads:[~2020-04-11 23:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 17:34 [PATCH] " Kamil Rytarowski
2020-03-19 13:07 ` Kamil Rytarowski
2020-03-20 15:36 ` Tom Tromey
2020-03-20 16:58 ` Kamil Rytarowski
2020-03-20 18:50 ` Tom Tromey
2020-03-20 19:13 ` Kamil Rytarowski
2020-03-25 16:36 ` John Baldwin
2020-03-26 23:24 ` Kamil Rytarowski
2020-03-20 16:58 ` [PATCH v2] " Kamil Rytarowski
2020-04-02 20:09 ` Kamil Rytarowski
2020-04-03 1:12 ` Kamil Rytarowski
2020-04-06 9:37 ` [PATCH v3] " Kamil Rytarowski
2020-04-10 10:20 ` Kamil Rytarowski
2020-04-11 21:05 ` Simon Marchi
2020-04-11 21:28 ` Kamil Rytarowski
2020-04-11 21:53 ` Simon Marchi
2020-04-11 23:45 ` [PATCH v4] " Kamil Rytarowski
2020-04-11 23:49 ` Simon Marchi [this message]
2020-04-12 0:09 ` Kamil Rytarowski
2020-04-12 0:09 ` [PATCH v5] " Kamil Rytarowski
2020-04-12 0:56 ` Simon Marchi
2020-04-12 10:17 ` Kamil Rytarowski
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=e027d897-8449-61c8-a715-47998e63e463@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=n54@gmx.com \
--cc=tom@tromey.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