From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: [commit] [patchv3] Fix SIGTERM signal safety (PR gdb/15358)
Date: Tue, 18 Mar 2014 21:51:00 -0000 [thread overview]
Message-ID: <20140318215109.GA30251@host2.jankratochvil.net> (raw)
In-Reply-To: <CADPb22Ta4YHXuBvuuQBY4gH_cX7yBnFWmaHuee8Rq_-G8fikfw@mail.gmail.com>
On Mon, 17 Mar 2014 23:35:21 +0100, Doug Evans wrote:
> On Sun, Mar 16, 2014 at 6:53 AM, Jan Kratochvil
> <jan.kratochvil@redhat.com> wrote:
> > gdb/
> > 2014-03-16 Jan Kratochvil <jan.kratochvil@redhat.com>
> >
> > PR gdb/15358
> > * defs.h (sync_quit_force_run): New declaration.
> > (QUIT): Check also SYNC_QUIT_FORCE_RUN.
> > * event-top.c (async_sigterm_handler): New declaration.
> > (async_sigterm_token): New variable.
> > (async_init_signals): Create also async_sigterm_token.
> > (async_sigterm_handler): New function.
> > (sync_quit_force_run): New variable.
> > (handle_sigterm): Replace quit_force call by other calls.
> > * utils.c (quit): Call quit_force if SYNC_QUIT_FORCE_RUN.
> >
> > gdb/testsuite/
> > 2014-03-16 Jan Kratochvil <jan.kratochvil@redhat.com>
> >
> > PR gdb/15358
> > * gdb.base/gdb-sigterm.c: New file.
> > * gdb.base/gdb-sigterm.exp: New file.
>
> Fine by me.
Checked in:
06c868a8dc5ef46ab7dd6601c8bc2f417e415af9
Thanks,
Jan
next prev parent reply other threads:[~2014-03-18 21:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 18:37 [patch] Fix SIGTERM signal safety (PR gdb/15358) [refresh] Jan Kratochvil
2014-03-14 18:45 ` [patchv2] " Jan Kratochvil
2014-03-15 19:44 ` Doug Evans
2014-03-16 13:53 ` [patchv3] Fix SIGTERM signal safety (PR gdb/15358) Jan Kratochvil
2014-03-17 22:35 ` Doug Evans
2014-03-18 21:51 ` Jan Kratochvil [this message]
2014-03-23 15:19 ` Yufeng Zhang
2014-03-23 16:58 ` Jan Kratochvil
2014-03-24 16:33 ` Yufeng Zhang
2014-03-24 17:11 ` [obv commit] " Jan Kratochvil
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=20140318215109.GA30251@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.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