From: Pedro Alves <pedro@palves.net>
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 4/5] gdb: print backtrace on fatal SIGSEGV
Date: Sun, 4 Jul 2021 01:53:03 +0100 [thread overview]
Message-ID: <94b1b365-6ccc-20bb-bd9a-5bccd15cd56e@palves.net> (raw)
In-Reply-To: <d610f11453e8756b366dbb2ddf852367a2ffabe9.1625223527.git.andrew.burgess@embecosm.com>
On 2021-07-02 12:06 p.m., Andrew Burgess wrote:
> 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".
(forgot to merge this comment with the other email)
Someone once said "A picture is worth a thousand words". :-)
Could you show us (and include in the commit log) an example of a GDB backtrace
we'd get?
next prev parent reply other threads:[~2021-07-04 0:53 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
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 [this message]
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=94b1b365-6ccc-20bb-bd9a-5bccd15cd56e@palves.net \
--to=pedro@palves.net \
--cc=andrew.burgess@embecosm.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).