public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Luke Diamand <ldiamand@roku.com>
To: elfutils-devel@sourceware.org
Cc: Florian Weimer <fweimer@redhat.com>, Luke Diamand <ldiamand@roku.com>
Subject: [RFC PATCH 0/1] In report_r_debug, iterate more segments
Date: Fri, 12 May 2023 08:02:17 +0100	[thread overview]
Message-ID: <20230512070218.761896-1-ldiamand@roku.com> (raw)

Further to:

    https://sourceware.org/pipermail/elfutils-devel/2023q2/006149.html

This is a draft patch to increase the number of iterations looking for
segments to load.

This lets eu-stack backtrace cores that would otherwise fail.

I have not included any unit tests as so far I have been unable to
reproduce the problem in a suitably small example.

Luke Diamand (1):
  report_r_debug: handle `-z separate-code' and find more modules

 libdwfl/link_map.c | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

-- 
2.39.1


             reply	other threads:[~2023-05-12  7:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12  7:02 Luke Diamand [this message]
2023-05-12  7:02 ` [RFC PATCH 1/1] report_r_debug: handle `-z separate-code' and find more modules Luke Diamand

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=20230512070218.761896-1-ldiamand@roku.com \
    --to=ldiamand@roku.com \
    --cc=elfutils-devel@sourceware.org \
    --cc=fweimer@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).