Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Aleksandar Ristovski <aristovski@qnx.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: patch: solib_break from _r_debug.r_brk
Date: Wed, 12 Oct 2011 21:16:00 -0000	[thread overview]
Message-ID: <20111012211613.GA25666@host1.jankratochvil.net> (raw)
In-Reply-To: <j61tbv$l88$1@dough.gmane.org>

On Thu, 29 Sep 2011 15:55:10 +0200, Aleksandar Ristovski wrote:
> I have a case where gdb can not find solib break function (in our
> case _dl_debug_state) in cases where dynamic linker library is
> stripped.

It would be an interesting patch but I do not see it useful on glibc:

$ readelf -Ws /lib64/ld-linux-x86-64.so.2
Symbol table '.dynsym' contains 28 entries:
   Num:    Value          Size Type    Bind   Vis      Ndx Name
    10: 0000000000223260    40 OBJECT  GLOBAL DEFAULT   21 _r_debug@@GLIBC_2.2.5
    18: 000000000000f610     2 FUNC    GLOBAL DEFAULT   11 _dl_debug_state@@GLIBC_PRIVATE

These symbols are the same category so if there is one, there will be both of
them.

Plus apparently `.dynsym' can never be `strip'ped.

So the patch may make sense for QNX and then one should just ensure it does
not break glibc.


Thanks,
Jan


      parent reply	other threads:[~2011-10-12 21:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-29 13:57 Aleksandar Ristovski
2011-09-29 14:04 ` Marek Polacek
2011-09-29 14:32   ` Aleksandar Ristovski
2011-09-29 15:15     ` Aleksandar Ristovski
2011-10-03 19:51       ` Aleksandar Ristovski
2011-10-03 20:12       ` Tom Tromey
2011-10-03 20:40         ` Aleksandar Ristovski
2011-10-04 16:58           ` Tom Tromey
2011-10-04 17:59             ` Aleksandar Ristovski
2011-10-10  2:32           ` Daniel Jacobowitz
2011-10-12 21:16 ` Jan Kratochvil [this message]

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=20111012211613.GA25666@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=aristovski@qnx.com \
    --cc=gdb-patches@sources.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