From: Pedro Alves <palves@redhat.com>
To: Antoine Tremblay <antoine.tremblay@ericsson.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] Fix lwp_suspend/unsuspend imbalance in linux_wait_1
Date: Thu, 01 Sep 2016 13:09:00 -0000 [thread overview]
Message-ID: <8a5b9633-43bc-6032-efad-dd64fc19bdd7@redhat.com> (raw)
In-Reply-To: <wwokshtkycj6.fsf@ericsson.com>
On 08/31/2016 08:16 PM, Antoine Tremblay wrote:
> BTW I always wanted to do this but never get to it, but it seems to me
> that it would be nice to have a --fatal-asserts flags in GDB that would
> create a core on assert.
>
> That way we could get a backtrace of the assert and know if we fixed a
> particular issue like this case.
I agree.
Calling exit() as done today is fatal too, so that's a bit ambiguous.
Maybe follow along gdb's "maintenance set internal-error {corefile,quit}",
and call it "--internal-error={corefile,quit}".
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-09-01 13:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 17:14 Antoine Tremblay
2016-08-31 17:14 ` [PATCH 2/2] Enable range stepping for ARM on GDBServer Antoine Tremblay
2016-08-31 17:50 ` Pedro Alves
2016-08-31 18:15 ` Antoine Tremblay
2016-08-31 18:39 ` Pedro Alves
2016-08-31 19:14 ` Antoine Tremblay
2016-09-01 13:37 ` Pedro Alves
2016-09-01 15:21 ` Antoine Tremblay
2016-09-01 15:59 ` Pedro Alves
2016-09-01 16:44 ` Yao Qi
2016-09-01 17:02 ` Pedro Alves
2016-09-01 17:06 ` Antoine Tremblay
2016-09-01 16:46 ` Antoine Tremblay
2016-09-18 19:58 ` Yao Qi
2016-08-31 17:40 ` [PATCH 1/2] Fix lwp_suspend/unsuspend imbalance in linux_wait_1 Pedro Alves
2016-08-31 17:50 ` Antoine Tremblay
2016-08-31 17:52 ` Pedro Alves
2016-08-31 18:25 ` Antoine Tremblay
2016-08-31 19:16 ` Antoine Tremblay
2016-09-01 13:09 ` Pedro Alves [this message]
2016-09-01 15:12 ` Antoine Tremblay
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=8a5b9633-43bc-6032-efad-dd64fc19bdd7@redhat.com \
--to=palves@redhat.com \
--cc=antoine.tremblay@ericsson.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