public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH v2 0/6] glibc-2.34: Fix gdb.base/gdb-sigterm.exp failure/error
Date: Sun, 22 Aug 2021 16:19:54 -0700	[thread overview]
Message-ID: <20210822231959.184061-1-kevinb@redhat.com> (raw)

The first patch in this series is the same as in v1.  Everything else
is new, though the problem, a regression in gdb.base/gdb-sigterm.exp
when run on a machine w/ glibc-2.34, being solved remains the same.

Kevin Buettner (6):
  Handle recursive internal problem in gdb_internal_error_resync
  Handle gdb SIGTERM via normal QUIT processing
  Catch and (re)throw gdb_exception_quit
  Python QUIT processing updates
  Guile QUIT processing updates
  QUIT processing w/ explicit sync_quit_force_run check

 gdb/ada-lang.c                   |  4 ++++
 gdb/breakpoint.c                 | 15 +++++++++++++++
 gdb/exceptions.c                 |  6 ++++++
 gdb/guile/scm-exception.c        |  4 ++++
 gdb/guile/scm-pretty-print.c     |  4 ++++
 gdb/guile/scm-type.c             |  4 ++++
 gdb/guile/scm-value.c            |  4 ++++
 gdb/i386-linux-tdep.c            |  4 ++++
 gdb/infrun.c                     |  4 ++++
 gdb/jit.c                        |  4 ++++
 gdb/mi/mi-main.c                 |  4 ++++
 gdb/objc-lang.c                  |  4 ++++
 gdb/parse.c                      |  4 ++++
 gdb/printcmd.c                   |  4 ++++
 gdb/python/py-finishbreakpoint.c |  6 ++++--
 gdb/python/py-gdb-readline.c     | 12 ++++++++----
 gdb/python/py-symbol.c           |  4 ++++
 gdb/python/py-utils.c            |  4 +++-
 gdb/python/py-value.c            |  4 ++++
 gdb/record-btrace.c              |  4 ++++
 gdb/remote-fileio.c              |  8 +++++++-
 gdb/solib.c                      |  4 ++++
 gdb/sparc64-linux-tdep.c         |  4 ++++
 gdb/testsuite/lib/gdb.exp        |  4 ++++
 gdb/utils.c                      |  5 +----
 25 files changed, 116 insertions(+), 12 deletions(-)

-- 
2.31.1


             reply	other threads:[~2021-08-22 23:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-22 23:19 Kevin Buettner [this message]
2021-08-22 23:19 ` [PATCH v2 1/6] Handle recursive internal problem in gdb_internal_error_resync Kevin Buettner
2021-09-27 17:38   ` Pedro Alves
2022-02-26 20:40     ` Kevin Buettner
2021-08-22 23:19 ` [PATCH v2 2/6] Handle gdb SIGTERM via normal QUIT processing Kevin Buettner
2021-09-27 17:39   ` Pedro Alves
2021-08-22 23:20 ` [PATCH v2 3/6] Catch and (re)throw gdb_exception_quit Kevin Buettner
2021-09-27 18:05   ` Pedro Alves
2021-08-22 23:20 ` [PATCH v2 4/6] Python QUIT processing updates Kevin Buettner
2021-09-27 18:24   ` Pedro Alves
2021-08-22 23:20 ` [PATCH v2 5/6] Guile " Kevin Buettner
2021-09-27 18:26   ` Pedro Alves
2021-08-22 23:20 ` [PATCH v2 6/6] QUIT processing w/ explicit sync_quit_force_run check Kevin Buettner
2021-09-27 18:34   ` Pedro Alves
2021-09-27 17:20 ` [PATCH v2 0/6] glibc-2.34: Fix gdb.base/gdb-sigterm.exp failure/error Kevin Buettner

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=20210822231959.184061-1-kevinb@redhat.com \
    --to=kevinb@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).