public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simon.marchi at polymtl dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30219] [native-gdbserver] FAIL: gdb.base/quit-live.exp: appear_how=run: extra_inferior=0: quit_how=sigterm: quit with SIGTERM (GDB internal error)
Date: Fri, 10 Mar 2023 19:35:11 +0000	[thread overview]
Message-ID: <bug-30219-4717-0DxmzQIJF6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30219-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30219

Simon Marchi <simon.marchi at polymtl dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kevinb at redhat dot com,
                   |                            |pedro at palves dot net

--- Comment #1 from Simon Marchi <simon.marchi at polymtl dot ca> ---
Started with:

Handle gdb SIGTERM by throwing / catching gdb_exception_force_quit
https://inbox.sourceware.org/gdb-patches/20230222234613.29662-3-kevinb@redhat.com/

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2023-03-10 19:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10 19:33 [Bug gdb/30219] New: " simon.marchi at polymtl dot ca
2023-03-10 19:35 ` simon.marchi at polymtl dot ca [this message]
2023-03-10 19:59 ` [Bug gdb/30219] " kevinb at redhat dot com
2023-03-10 20:00 ` kevinb at redhat dot com
2023-03-30 21:59 ` cvs-commit at gcc dot gnu.org
2023-03-30 22:22 ` kevinb at redhat dot com

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=bug-30219-4717-0DxmzQIJF6@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).