From: Andreas Schwab <schwab@linux-m68k.org>
To: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
Cc: Florian Weimer <fweimer@redhat.com>,
"xe-linux-external\(mailer list\)" <xe-linux-external@cisco.com>,
"Jeremy Stenglein \(jstengle\)" <jstengle@cisco.com>,
Pedro Alves <palves@redhat.com>
Subject: Re: [RFC PATCH 0/3] implement dlmopen hooks for gdb
Date: Tue, 22 Sep 2020 20:17:10 +0200 [thread overview]
Message-ID: <87ft79ptg9.fsf@igel.home> (raw)
In-Reply-To: <b2362e0e-ed6f-e5c5-c6fe-e1b06e14571a@redhat.com> (Carlos O'Donell via Libc-alpha's message of "Tue, 22 Sep 2020 13:59:09 -0400")
On Sep 22 2020, Carlos O'Donell via Libc-alpha wrote:
> Yes, absolutely, I agree completely, for it to be useful the semantics
> have to be:
>
> - If you detect a given symbol foo@GLIBC_DEBUG, then the feature is
> present and has the semantics you expect.
>
> - If you want new semantics then you need to make a foo2@GLIBC_DEBUG
> with the new semantics.
>
> What are the runtime semantics of the symbol? How do you access it?
Isn't that the same situation as libthread_db?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2020-09-22 18:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 19:32 [RFC PATCH 0/3] implement dlmopen hooks for gdb Daniel Walker via Libc-alpha
2020-06-26 21:17 ` Carlos O'Donell via Libc-alpha
2020-07-23 18:40 ` Daniel Walker (danielwa) via Libc-alpha
2020-07-23 21:20 ` Carlos O'Donell via Libc-alpha
2020-09-16 16:18 ` Daniel Walker (danielwa) via Libc-alpha
2020-09-17 12:52 ` Carlos O'Donell via Libc-alpha
2020-09-17 12:59 ` Florian Weimer via Libc-alpha
2020-09-17 13:53 ` Carlos O'Donell via Libc-alpha
2020-09-18 15:35 ` Daniel Walker (danielwa) via Libc-alpha
2020-09-18 15:40 ` Florian Weimer via Libc-alpha
2020-09-21 20:02 ` Daniel Walker (danielwa) via Libc-alpha
2021-07-28 18:33 ` Daniel Walker via Libc-alpha
2021-07-28 18:48 ` H.J. Lu via Libc-alpha
2020-09-17 13:52 ` Carlos O'Donell via Libc-alpha
2020-09-22 17:06 ` Florian Weimer via Libc-alpha
2020-09-22 17:28 ` Carlos O'Donell via Libc-alpha
2020-09-22 17:37 ` Florian Weimer via Libc-alpha
2020-09-22 17:59 ` Carlos O'Donell via Libc-alpha
2020-09-22 18:04 ` Florian Weimer via Libc-alpha
2020-09-22 18:41 ` Carlos O'Donell via Libc-alpha
2020-09-22 18:44 ` Florian Weimer via Libc-alpha
2020-09-22 18:46 ` Carlos O'Donell via Libc-alpha
2020-09-22 18:17 ` Andreas Schwab [this message]
2020-09-22 19:13 ` Carlos O'Donell via Libc-alpha
2020-06-26 21:30 ` Florian Weimer via Libc-alpha
2020-06-27 1:10 ` Daniel Walker (danielwa) via Libc-alpha
2020-07-02 13:54 ` Conan Huang (conhuang) via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ft79ptg9.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=fweimer@redhat.com \
--cc=jstengle@cisco.com \
--cc=libc-alpha@sourceware.org \
--cc=palves@redhat.com \
--cc=xe-linux-external@cisco.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).