From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Snyder <msnyder@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFC] Add back the 'info proc mappings' command.
Date: Sun, 23 Dec 2001 13:12:00 -0000 [thread overview]
Message-ID: <20011223161149.A6649@nevyn.them.org> (raw)
In-Reply-To: <200112212259.OAA18720@cleaver.cygnus.com>
On Fri, Dec 21, 2001 at 02:59:53PM -0800, Michael Snyder wrote:
>
> This adds back a sub-command ('mappings') of the "info proc"
> command, which was lost a couple years ago when procfs.c was
> rewritten. There are a bunch of other sub-commands that could
> also be added back in -- I just happened to need this one.
>
> I'll wait a week for objections before I check it in.
>
> 2001-12-21 Michael Snyder <msnyder@redhat.com>
>
> * procfs.c (info_proc_cmd): Add the 'mappings' sub-command that
> was dropped a few years ago, when procfs.c was rewritten.
> (info_proc_mappings): New function, implent 'info proc mappings'.
> (mappingflags): New function.
> (_initialize_procfs): Document new option to 'info proc' command.
>
> Index: procfs.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/procfs.c,v
> retrieving revision 1.32
> diff -c -3 -p -r1.32 procfs.c
> *** procfs.c 2001/07/07 21:55:28 1.32
> --- procfs.c 2001/12/21 22:57:30
> *************** proc_set_watchpoint (procinfo *pi, CORE_
> *** 2879,2889 ****
> * or zero.
> */
>
> - /* FIXME: it's probably a waste to cache this FD.
> - It doesn't get called that often... and if I open it
> - every time, I don't need to lseek it. */
> int
> ! proc_iterate_over_mappings (int (*func) (int, CORE_ADDR))
> {
> struct prmap *map;
> procinfo *pi;
> --- 2879,2886 ----
> * or zero.
> */
>
> int
> ! proc_iterate_over_mappings (int (*func) (int, CORE_ADDR)
> {
> struct prmap *map;
> procinfo *pi;
That's a typo, I think - you deleted a parenthesis. Did this compile?
Looks fine to me otherwise, FWIW.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-12-23 21:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-21 15:00 Michael Snyder
2001-12-23 4:13 ` Eli Zaretskii
2001-12-26 11:22 ` Michael Snyder
2001-12-26 11:27 ` Michael Snyder
2001-12-26 11:34 ` Michael Snyder
2001-12-26 12:29 ` Eli Zaretskii
2001-12-26 14:28 ` Michael Snyder
2001-12-27 0:49 ` Eli Zaretskii
2001-12-27 10:43 ` Michael Snyder
2001-12-29 11:17 ` Andrew Cagney
2001-12-23 13:12 ` Daniel Jacobowitz [this message]
2001-12-28 11:48 ` Michael Snyder
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=20011223161149.A6649@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@cygnus.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