unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Walker via Libc-alpha <libc-alpha@sourceware.org>
To: libc-alpha@sourceware.org
Cc: Jeremy Stenglein <jstengle@cisco.com>, xe-linux-external@cisco.com
Subject: [RFC PATCH 0/3] implement dlmopen hooks for gdb
Date: Fri, 26 Jun 2020 12:32:25 -0700	[thread overview]
Message-ID: <20200626193228.1953-1-danielwa@cisco.com> (raw)

Cisco System, Inc. has a need to have dlmopen support in gdb, which
required glibc changes. I think it was known when glibc implemented
dlmopen that gdb would not work with it.

Since 2015 Cisco has had these patches in our inventor to fix issues in
glibc which prevented this type of gdb usage.

This RFC is mainly to get guidance on this implementation. We have some
individuals who have signed the copyright assignment for glibc, and we
will submit these (or different patches) formally thru those channels if
no one has issues with the implementation.

Also included in this are a couple of fixes which went along with the
original implementation.

Please provide any comments you might have.

Conan C Huang (3):
  Segfault when dlopen with RTLD_GLOBAL in dlmopened library
  glibc: dlopen RTLD_NOLOAD optimization
  add r_debug multiple namespaces support

 elf/dl-close.c |  7 ++++++-
 elf/dl-debug.c | 13 ++++++++++---
 elf/dl-open.c  |  8 +++++++-
 elf/link.h     |  4 ++++
 4 files changed, 27 insertions(+), 5 deletions(-)

-- 
2.17.1


             reply	other threads:[~2020-06-26 19:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-26 19:32 Daniel Walker via Libc-alpha [this message]
2020-06-26 21:17 ` [RFC PATCH 0/3] implement dlmopen hooks for gdb 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
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=20200626193228.1953-1-danielwa@cisco.com \
    --to=libc-alpha@sourceware.org \
    --cc=danielwa@cisco.com \
    --cc=jstengle@cisco.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).