public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 3/4] Provide access to non SEC_HAS_CONTENTS core file sections
Date: Wed, 25 Mar 2020 10:25:09 -0700	[thread overview]
Message-ID: <4f8f93e1-8cb6-9303-c038-d85218eb1990@redhat.com> (raw)
In-Reply-To: <20200305004243.334607-4-kevinb@redhat.com>

On 3/4/20 4:42 PM, Kevin Buettner wrote:

[snip excellent introduction to the problem]

> What we should be doing is this:
> 
> - Attempt to access core file data for SEC_HAS_CONTENTS sections.
> - Attempt to access executable file data if the above fails.
> - Attempt to access core file data for non SEC_HAS_CONTENTS sections, if
>   both of the above fail.

This is also the path that I was investigating. FWIW, I don't see
anything obviously `wrong' with the contents of the patch, but low-level
target operations are outside where I typically work.

Just one trivial request (again):

> gdb/ChangeLog:
> 

+ PR corefiles/25631

> 	* corelow.c (class core_target): Add new field> 	m_core_no_contents_section_table.
> 	(core_target::core_target): Initialize
> 	m_core_no_contents_section_table.
> 	(core_target::~core_target): Free data structure associated
> 	with m_core_no_contents_section_table.
> 	(core_target::files_info): Print section info associated with
> 	m_core_no_contents_section_table.
> 	(core_target:xfer_partial): Revise TARGET_OBJECT_MEMORY case
> 	to consider the stratum beneath the core target as well as
> 	m_core_no_contents_section_table.

Keith


  reply	other threads:[~2020-03-25 17:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05  0:43 [PATCH 0/4] Fix BZ 25631 - core file memory access problem Kevin Buettner
2020-03-05  0:43 ` [PATCH 4/4] Test ability to access unwritten-to mmap data in core file Kevin Buettner
2020-03-25 17:25   ` Keith Seitz
2020-03-05  0:43 ` [PATCH 2/4] Add function for partitioning/splitting a section table Kevin Buettner
2020-03-25 17:25   ` Keith Seitz
2020-03-05  0:43 ` [PATCH 1/4] Remove hack for GDB which sets the section size to 0 Kevin Buettner
2020-03-18 16:28   ` Kevin Buettner
2020-05-04 18:09   ` Jan Kratochvil
2020-03-05  0:43 ` [PATCH 3/4] Provide access to non SEC_HAS_CONTENTS core file sections Kevin Buettner
2020-03-25 17:25   ` Keith Seitz [this message]
2020-03-29 13:18   ` Pedro Alves
2020-05-03  7:21     ` Kevin Buettner
2020-05-03 11:07       ` H.J. Lu
2020-05-03 19:06         ` Kevin Buettner
2020-05-12  8:40     ` Kevin Buettner
2020-05-13 17:44       ` Kevin Buettner
2020-05-20 12:05       ` Pedro Alves
2020-05-20 16:04       ` Pedro Alves
2020-03-18 16:29 ` [PATCH 0/4] Fix BZ 25631 - core file memory access problem Kevin Buettner

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=4f8f93e1-8cb6-9303-c038-d85218eb1990@redhat.com \
    --to=keiths@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).