public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/15358] gdb deadlock due to gdb calling calloc() in signal handler. Date: Tue, 18 Mar 2014 21:51:00 -0000 [thread overview] Message-ID: <bug-15358-4717-A1lTw7utTb@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15358-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=15358 --- Comment #6 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gdb and binutils". The branch, master has been updated via 06c868a8dc5ef46ab7dd6601c8bc2f417e415af9 (commit) from dea80df0999ae0bad56e79af2a88a30be38bb8e4 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=06c868a8dc5ef46ab7dd6601c8bc2f417e415af9 commit 06c868a8dc5ef46ab7dd6601c8bc2f417e415af9 Author: Jan Kratochvil <jan.kratochvil@redhat.com> Date: Tue Mar 18 22:48:06 2014 +0100 Fix SIGTERM signal safety (PR gdb/15358). gdb/ 2014-03-18 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-18 Jan Kratochvil <jan.kratochvil@redhat.com> PR gdb/15358 * gdb.base/gdb-sigterm.c: New file. * gdb.base/gdb-sigterm.exp: New file. Message-ID: <20140316135334.GA30698@host2.jankratochvil.net> ----------------------------------------------------------------------- Summary of changes: gdb/ChangeLog | 13 ++++ gdb/defs.h | 5 +- gdb/event-top.c | 27 ++++++++- gdb/testsuite/ChangeLog | 6 ++ gdb/testsuite/gdb.base/gdb-sigterm.c | 26 +++++++++ gdb/testsuite/gdb.base/gdb-sigterm.exp | 96 ++++++++++++++++++++++++++++++++ gdb/utils.c | 6 ++ 7 files changed, 176 insertions(+), 3 deletions(-) create mode 100644 gdb/testsuite/gdb.base/gdb-sigterm.c create mode 100644 gdb/testsuite/gdb.base/gdb-sigterm.exp -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-03-18 21:51 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-11 15:02 [Bug gdb/15358] New: " xavier.bru at bull dot net 2013-04-12 8:35 ` [Bug gdb/15358] " jan.kratochvil at redhat dot com 2013-04-15 5:10 ` xavier.bru at bull dot net 2013-06-17 6:30 ` jan.kratochvil at redhat dot com 2013-06-17 14:00 ` tromey at redhat dot com 2013-07-01 20:36 ` jan.kratochvil at redhat dot com 2013-07-03 5:31 ` jan.kratochvil at redhat dot com 2014-03-14 18:38 ` jan.kratochvil at redhat dot com 2014-03-14 18:46 ` jan.kratochvil at redhat dot com 2014-03-18 21:51 ` cvs-commit at gcc dot gnu.org [this message] 2014-03-18 21:52 ` jan.kratochvil at redhat dot com 2023-02-15 21:34 ` pedro at palves dot net
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=bug-15358-4717-A1lTw7utTb@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).