From: Michael Snyder <msnyder@redhat.com>
To: Nora Pan <qpan@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Patch: Fix the segment missing in gcore maps parser.
Date: Mon, 21 Mar 2005 19:23:00 -0000 [thread overview]
Message-ID: <423F1F1B.3040803@redhat.com> (raw)
In-Reply-To: <000201c52db0$b6ef5780$810a000a@Nora>
Nora Pan wrote:
> A bug in gdb /proc/<pid>/maps parser causes gcore can't capture the
> segments following the one with a file name and zero inode entry in the
> maps file. For example:
>
> 30028000-3002f000 rw-s 00000000 00:05 0 /SYSV0000bdad (deleted)
>
> Okay for mainline?
Well, as the gcore author, it looks fine to me.
Any linux native maintainers object?
next prev parent reply other threads:[~2005-03-21 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 0:55 Nora Pan
2005-03-21 19:23 ` Michael Snyder [this message]
2005-03-21 21:00 ` Daniel Jacobowitz
2005-05-18 20:53 ` Nora Pan
2005-05-24 1:04 ` 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=423F1F1B.3040803@redhat.com \
--to=msnyder@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=qpan@mvista.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