From: Michael Snyder <msnyder@vmware.com>
To: Hui Zhu <teawater@gmail.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: About the gdb prec save/restore reverse exec behavior error (gcore error)
Date: Wed, 04 Nov 2009 18:29:00 -0000 [thread overview]
Message-ID: <4AF1C806.2010802@vmware.com> (raw)
In-Reply-To: <daef60380911032255o33f4f38dgf531e13d87818f30@mail.gmail.com>
Hui Zhu wrote:
> Hi Michael,
>
> I make a patch to fix it. I try in i386-ubuntu. It is OK now.
> Please help me review it.
>
> Thanks,
> Hui
>
> 2009-11-04 Hui Zhu <teawater@gmail.com>
>
> * gcore.c (gcore_copy_callback): Remove bfd_get_section_flags check.
>
> ---
> gcore.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> --- a/gcore.c
> +++ b/gcore.c
> @@ -510,10 +510,6 @@ gcore_copy_callback (bfd *obfd, asection
> struct cleanup *old_chain = NULL;
> void *memhunk;
>
> - /* Read-only sections are marked; we don't have to copy their contents. */
> - if ((bfd_get_section_flags (obfd, osec) & SEC_LOAD) == 0)
> - return;
> -
> /* Only interested in "load" sections. */
> if (strncmp ("load", bfd_section_name (obfd, osec), 4) != 0)
> return;
>
No, this is not acceptable. We can't save ALL of the loadable
sections, it will make the gcore file much bigger than necessary.
Most loadable sections are code, and do not need to be saved.
We will need to choose explicitly just the loadable sections
that we need to save.
next prev parent reply other threads:[~2009-11-04 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 17:41 Hui Zhu
[not found] ` <4AEC74B8.9090908@vmware.com>
2009-11-04 6:56 ` Hui Zhu
2009-11-04 18:29 ` Michael Snyder [this message]
2009-11-05 2:24 ` Hui Zhu
2009-11-05 2:26 ` Hui Zhu
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=4AF1C806.2010802@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb@sourceware.org \
--cc=teawater@gmail.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