public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: John Baldwin <jhb@FreeBSD.org>
To: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Test stepping within a runtime loader / dynamic linker
Date: Mon, 10 Oct 2022 11:45:03 -0700	[thread overview]
Message-ID: <cef33817-0ca3-0a63-58bd-b710fd60e976@FreeBSD.org> (raw)
In-Reply-To: <20221008035716.46147-3-kevinb@redhat.com>

On 10/7/22 8:57 PM, Kevin Buettner via Gdb-patches wrote:
> See the remarks in rtld-step.exp for a description of what this
> test is about.
> 
> This test case has been tested using gcc on the following x86-64 Linux
> distributions/releases:
> 
>      Fedora 28
>      Fedora 32
>      Fedora 33
>      Fedora 34
>      Fedora 35
>      Fedora 36
>      Fedora 37
>      rawhide (f38)
>      RHEL 9.1
>      Ubuntu 22.04.1 LTS
> 
> It's also been tested (and found to be working) with
> RUNTESTFLAGS="CC_FOR_TARGET=clang" on all of the above expect for
> Fedora 28.  The (old) version of clang available on F28 did not
> accept the -static-pie option.
> 
> I also tried to make this test work on FreeBSD 13.1.  While I think I
> made significant progress, I was ultimately stymied by this message
> which occurs when attempting to run the main program which has been
> set to use the fake/pretend RTLD as the ELF interpreter:
> 
> ELF interpreter /path/to/rtld-step-rtld not found, error 22
> 
> I have left one of the flags (-static) in place which I believe
> to be needed for FreeBSD (though since I never got it to work, I
> don't know for sure.)  I've also left some declarations needed
> for FreeBSD in rtld-step-rtld.c.  They're currently disabled via
> a #if 0; you'll need to enable them if you want to try to make
> it work on FreeBSD.

Hmm, thanks for testing on FreeBSD.  FreeBSD currently doesn't support
static PIE binaries, so I think the failure you ran into is not
unexpected.

In terms of the feature, this is indeed useful (I sometimes need to
step inside rtld myself).  I think your implementation in patch 1 makes
sense.

-- 
John Baldwin

  reply	other threads:[~2022-10-10 18:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-08  3:57 [PATCH 0/2] Allow debugging of " Kevin Buettner
2022-10-08  3:57 ` [PATCH 1/2] " Kevin Buettner
2022-11-03 15:52   ` Lancelot SIX
2022-10-08  3:57 ` [PATCH 2/2] Test stepping within a " Kevin Buettner
2022-10-10 18:45   ` John Baldwin [this message]
2022-10-20  2:42     ` 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=cef33817-0ca3-0a63-58bd-b710fd60e976@FreeBSD.org \
    --to=jhb@freebsd.org \
    --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).