Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Roland McGrath <roland@frob.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: gnu-nat.c patch mangled
Date: Tue, 30 Apr 2002 12:05:00 -0000	[thread overview]
Message-ID: <3CCEE743.F8E9C328@redhat.com> (raw)
In-Reply-To: <20020430182655.8880E1BA15@perdition.linnaean.org>

Roland McGrath wrote:
> 
> My patch to gdb/gnu-nat.c (committed in rev 1.20) did not make it intact.
> 
> This patch vs the current file is needed to properly effect the changes
> from my original patch.  I'm not including an extra log entry since this
> was part of the same change I submitted.  I don't know how it got lost
> in the commit.

Sorry, Roland.  Committed.

> 
> Index: gnu-nat.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/gnu-nat.c,v
> retrieving revision 1.20
> diff -u -b -p -r1.20 gnu-nat.c
> --- gnu-nat.c   24 Apr 2002 21:44:46 -0000      1.20
> +++ gnu-nat.c   30 Apr 2002 18:22:51 -0000
> @@ -2536,6 +2536,16 @@ gnu_find_memory_regions (int (*func) (CO
>           last_protection = protection;
>         }
>      }
> +
> +  /* Report the final region.  */
> +  if (last_region_end > last_region_address && last_protection != VM_PROT_NONE)
> +    (*func) (last_region_address, last_region_end - last_region_address,
> +            last_protection & VM_PROT_READ,
> +            last_protection & VM_PROT_WRITE,
> +            last_protection & VM_PROT_EXECUTE,
> +            data);
> +
> +  return 0;
>  }
> 
>


      reply	other threads:[~2002-04-30 19:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-30 11:27 Roland McGrath
2002-04-30 12:05 ` Michael Snyder [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=3CCEE743.F8E9C328@redhat.com \
    --to=msnyder@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=roland@frob.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