public inbox for infinity@sourceware.org
 help / color / mirror / Atom feed
From: Gary Benson <gbenson@redhat.com>
To: infinity@sourceware.org
Subject: First Infinity full-system preview now available
Date: Mon, 13 Jun 2016 09:32:00 -0000	[thread overview]
Message-ID: <20160613093200.GA29173@blade.nx> (raw)

Over the past few weeks I've been working on a full-system preview
release of Infinity.  It's now available:

  https://infinitynotes.org/wiki/First_Flight

This release comprises just enough of Infinity for GDB to attach to a
live process or start with a core file.  "info threads" should work,
"print errno" does not.

The page linked above details how to:

 * Build glibc with Infinity notes for thread debugging
 * Run applications using that glibc.
 * Use unmodified GDB to debug those applications using Infinity.

All this can be done as a normal user (root access is not required).

This release should allow you to see what Infinity notes look like in
the field.  The notes in this release add 880 bytes to libpthread.so
on x86_64.  This is probably about half of what GDB needs to replicate
what it needs from libthread_db, so I expect the final overhead to be
about 1.7k (some of which will be in the runtime linker).  Please note
that Infinity notes are NOT mapped into memory.

This preview uses a libthread_db shim that calls into the Infinity
client library libi8x.  This shim exists for the purposes of this
preview release only: there are NO current plans to make this shim
suitable for production use: clients that wish to access libpthread
internals via a libthread_db-style interface can continue to use the
libthread_db.so provided by glibc.

Please direct questions to infinity@sourceware.org.

Thanks!
Gary

-- 
https://infinitynotes.org/

                 reply	other threads:[~2016-06-13  9:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160613093200.GA29173@blade.nx \
    --to=gbenson@redhat.com \
    --cc=infinity@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).