Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Gary Benson <gbenson@redhat.com>
Cc: gdb-patches@sourceware.org, aburgess@broadcom.com,
	xdje42@gmail.com, fw@deneb.enyo.de, mark.kettenis@xs4all.nl,
	palves@redhat.com, tromey@redhat.com
Subject: Re: [PATCH 3/3 v5] Demangler crash handler
Date: Mon, 09 Jun 2014 16:20:00 -0000	[thread overview]
Message-ID: <83sine12cs.fsf@gnu.org> (raw)
In-Reply-To: <20140609152434.GD27494@blade.nx>

> Date: Mon, 9 Jun 2014 16:24:34 +0100
> From: Gary Benson <gbenson@redhat.com>
> Cc: Andrew Burgess <aburgess@broadcom.com>, Doug Evans <xdje42@gmail.com>,
>         Eli Zaretskii <eliz@gnu.org>, Florian Weimer <fw@deneb.enyo.de>,
>         Mark Kettenis <mark.kettenis@xs4all.nl>,
>         Pedro Alves <palves@redhat.com>, Tom Tromey <tromey@redhat.com>
> 
> This patch wraps calls to the demangler with a segmentation fault
> handler.  The first time a segmentation fault is caught a core file
> is generated and the user is prompted to file a bug and offered the
> choice to exit or to continue their GDB session.  A maintainence
> option is provided to allow the user to disable the crash handler
> if required.

OK for the documentation part.

Thanks.


  reply	other threads:[~2014-06-09 16:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09 15:22 [PATCH 0/3 " Gary Benson
2014-06-09 15:23 ` [PATCH 1/3 v5] Add new internal problem for demangler warnings Gary Benson
2014-06-09 16:19   ` Eli Zaretskii
2014-06-09 15:24 ` [PATCH 2/3 v5] Refactor and expose core-dumping functionality Gary Benson
2014-06-09 15:24 ` [PATCH 3/3 v5] Demangler crash handler Gary Benson
2014-06-09 16:20   ` Eli Zaretskii [this message]
2014-06-09 18:25     ` Gary Benson
2014-07-14  0:31   ` Cygwin build failure following " Pierre Muller
2014-07-14  8:52     ` Corinna Vinschen
2014-07-14 12:10       ` Gary Benson
2014-07-14  8:54     ` Gary Benson
2014-07-14 10:28       ` Andreas Schwab
     [not found]         ` <20140714114241.GA31867@blade.nx>
2014-07-14 16:13           ` Tom Tromey
2014-07-14 17:52           ` Pierre Muller
2014-06-11 20:41 ` [PATCH 0/3 " Tom Tromey
2014-06-11 21:03   ` Mark Kettenis
2014-06-19  8:23   ` [COMMITTED PATCH " Gary Benson

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=83sine12cs.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=aburgess@broadcom.com \
    --cc=fw@deneb.enyo.de \
    --cc=gbenson@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=palves@redhat.com \
    --cc=tromey@redhat.com \
    --cc=xdje42@gmail.com \
    /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