public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@scylladb.com>
To: gdb@sourceware.org
Subject: debuginfod vs libthread_db.so
Date: Thu, 24 Nov 2022 14:02:03 +0200	[thread overview]
Message-ID: <f1a60704b0f2f8ca9ad96ddc137360ae7557aaf6.camel@scylladb.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 689 bytes --]

debuginfod is pretty nice, since it allows you to debug a core file
generated on one system on another, without worrying about debug
information, so long as you point your debuginfod settings in the right
direction.

However, will it work for libthread_db.so? If not, then this breaks
down if the two systems use different libc versions that have
incompatible libthread_db.so.


(tangent: is it possible to express libthread_db.so code as DWARF
expressions? if so it will be possible to get rid of libthread_db.so,
by having libc encode accessors to thread information as some DWARF
expressions, and teaching gdb to use those expressions instead of
calling libthread_db.so)

             reply	other threads:[~2022-11-24 12:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 12:02 Avi Kivity [this message]
2022-11-24 12:24 ` Mark Wielaard
2022-11-30 18:46   ` Florian Weimer

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=f1a60704b0f2f8ca9ad96ddc137360ae7557aaf6.camel@scylladb.com \
    --to=avi@scylladb.com \
    --cc=gdb@sourceware.org \
    /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).