From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@palves.net>
Cc: andrew.burgess@embecosm.com, gdb-patches@sourceware.org
Subject: Re: [PATCH 4/5] gdb: print backtrace on fatal SIGSEGV
Date: Sun, 04 Jul 2021 07:32:18 +0300 [thread overview]
Message-ID: <837di6itrh.fsf@gnu.org> (raw)
In-Reply-To: <557e4fe7-6fab-10aa-635e-73c874230d67@palves.net> (message from Pedro Alves on Sun, 4 Jul 2021 01:55:02 +0100)
> From: Pedro Alves <pedro@palves.net>
> Cc: gdb-patches@sourceware.org
> Date: Sun, 4 Jul 2021 01:55:02 +0100
>
> On 2021-07-02 12:47 p.m., Eli Zaretskii via Gdb-patches wrote:
> >> From: Andrew Burgess <andrew.burgess@embecosm.com>
> >> Date: Fri, 2 Jul 2021 12:06:07 +0100
> >> So, currently, this is only effecting our handling of SIGSEGV.
> >> Previously, if GDB hit a SEGV then we would terminate GDB with a
> >> SIGABRT. After this commit we will terminate GDB with a SIGSEGV.
> >> This feels like an improvement to me, we should still get a core dump,
> >> but in many shells, the user will see a more specific message once GDB
> >> exits, in bash for example "Segmentation fault" rather than "Aborted".
>
> > But will GDB still present the "internal error, submit a bug report"
> > message when a fatal signal such as SIGSEGV is encountered?
> >
>
> Your use of "still" seems to imply that that's what happens today, but it
> isn't. GDB currently just aborts, no questions asked.
And the answer to the _real_ question I asked is...?
next prev parent reply other threads:[~2021-07-04 4:32 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 11:06 [PATCH 0/5] GDB Synchronous Signal Handling Andrew Burgess
2021-07-02 11:06 ` [PATCH 1/5] gdb: terminate upon receipt of SIGFPE Andrew Burgess
2021-07-02 12:09 ` Eli Zaretskii
2021-07-02 18:11 ` Tom Tromey
2021-07-02 22:51 ` Pedro Alves
2021-07-03 6:14 ` Eli Zaretskii
2021-07-03 18:02 ` Pedro Alves
2021-07-03 18:23 ` Eli Zaretskii
2021-07-03 22:52 ` Pedro Alves
2021-07-04 4:27 ` Eli Zaretskii
2021-07-04 14:51 ` Pedro Alves
2021-07-04 16:31 ` Eli Zaretskii
2021-07-03 22:58 ` Pedro Alves
2021-07-02 11:06 ` [PATCH 2/5] gdb: register signal handler after setting up event token Andrew Burgess
2021-07-03 23:02 ` Pedro Alves
2021-07-02 11:06 ` [PATCH 3/5] gdb: rewrite header comment on async_init_signals Andrew Burgess
2021-07-03 23:23 ` Pedro Alves
2021-07-02 11:06 ` [PATCH 4/5] gdb: print backtrace on fatal SIGSEGV Andrew Burgess
2021-07-02 11:47 ` Eli Zaretskii
2021-07-04 0:55 ` Pedro Alves
2021-07-04 4:32 ` Eli Zaretskii [this message]
2021-07-04 14:32 ` Pedro Alves
2021-07-04 14:38 ` Eli Zaretskii
2021-07-04 15:03 ` Pedro Alves
2021-07-04 16:34 ` Eli Zaretskii
2021-07-04 0:51 ` Pedro Alves
2021-07-04 0:53 ` Pedro Alves
2021-07-02 11:06 ` [PATCH 5/5] gdb: register SIGBUS, SIGFPE, and SIGABRT handlers Andrew Burgess
2021-07-04 0:58 ` Pedro Alves
2021-07-21 18:08 ` [PATCHv2 0/6] GDB Synchronous Signal Handling Andrew Burgess
2021-07-21 18:08 ` [PATCHv2 1/6] gdb: terminate upon receipt of SIGFPE Andrew Burgess
2021-07-21 18:08 ` [PATCHv2 2/6] gdb: register signal handler after setting up event token Andrew Burgess
2021-07-21 18:08 ` [PATCHv2 3/6] gdb: rename async_init_signals to gdb_init_signals Andrew Burgess
2021-07-21 18:08 ` [PATCHv2 4/6] gdb: print backtrace on fatal SIGSEGV Andrew Burgess
2021-08-10 18:53 ` Pedro Alves
2021-07-21 18:08 ` [PATCHv2 5/6] gdb: register SIGBUS, SIGFPE, and SIGABRT handlers Andrew Burgess
2021-07-21 18:08 ` [PATCHv2 6/6] gdb: don't print backtrace when dumping core after an internal error Andrew Burgess
2021-07-27 18:54 ` [PATCHv2 0/6] GDB Synchronous Signal Handling Tom Tromey
2021-08-10 9:33 ` Andrew Burgess
2021-08-10 18:56 ` 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=837di6itrh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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).