public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/3] Work around PR libc/13097 "linux-vdso.so.1"
Date: Fri, 26 Sep 2014 12:25:00 -0000	[thread overview]
Message-ID: <1411734329-4707-1-git-send-email-palves@redhat.com> (raw)

Following up to:
  https://sourceware.org/ml/gdb-patches/2014-09/msg00777.html

This series works around PR libc/13097 in GDB.  See patch 2/3 for
details.

Pedro Alves (3):
  Split vDSO range lookup to a gdbarch hook
  Work around PR libc/13097 "linux-vdso.so.1"
  Cache the vsyscall/vDSO range per-inferior

 gdb/arch-utils.c                        |   8 ++
 gdb/arch-utils.h                        |   4 +
 gdb/gdbarch.c                           |  23 ++++++
 gdb/gdbarch.h                           |  10 +++
 gdb/gdbarch.sh                          |   7 ++
 gdb/linux-tdep.c                        | 133 ++++++++++++++++++++++++++++++++
 gdb/memrange.c                          |   9 +++
 gdb/memrange.h                          |   5 ++
 gdb/solib-svr4.c                        |  81 ++++++++++++++++++-
 gdb/symfile-mem.c                       |  31 ++------
 gdb/testsuite/gdb.base/vdso-warning.c   |  22 ++++++
 gdb/testsuite/gdb.base/vdso-warning.exp |  54 +++++++++++++
 12 files changed, 359 insertions(+), 28 deletions(-)
 create mode 100644 gdb/testsuite/gdb.base/vdso-warning.c
 create mode 100644 gdb/testsuite/gdb.base/vdso-warning.exp

-- 
1.9.3

             reply	other threads:[~2014-09-26 12:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26 12:25 Pedro Alves [this message]
2014-09-26 12:25 ` [PATCH 1/3] Split vDSO range lookup to a gdbarch hook Pedro Alves
2014-09-26 12:25 ` [PATCH 3/3] Cache the vsyscall/vDSO range per-inferior Pedro Alves
2014-09-26 12:25 ` [PATCH 2/3] Work around PR libc/13097 "linux-vdso.so.1" Pedro Alves
2014-10-10 16:14 ` [PATCH 0/3] " Pedro Alves

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=1411734329-4707-1-git-send-email-palves@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@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).