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 guile/17185] hang with libgc 7.4.0 Date: Sat, 26 Jul 2014 21:51:00 -0000 [thread overview] Message-ID: <bug-17185-4717-J6yL96UBh4@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17185-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17185 --- Comment #1 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 74edf51613b507d1f27d66360cd8fdd8a253e88a (commit) from e57e6ddc2e768323732a7eed6a5d25d3ee350638 (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=74edf51613b507d1f27d66360cd8fdd8a253e88a commit 74edf51613b507d1f27d66360cd8fdd8a253e88a Author: Doug Evans <xdje42@gmail.com> Date: Sat Jul 26 14:49:04 2014 -0700 PR 17185 PR 17185 describes a problem with using gdb+guile with libgc 7.4.0. The symptom is a hang in sigsuspend. [The thread referenced in the PR has the details.] It's not clear what the right fix is, or even where the bug is yet. This patch applies the same workaround Guile has applied. There is no functionality or real performance loss with this, and Guile has been using it for awhile. * configure.ac: Add check for header gc/gc.h. Add check for function setenv. * configure: Regenerate. * config.in: Regenerate. * guile/guile.c (_initialize_guile): Add workaround for libgc 7.4.0. ----------------------------------------------------------------------- Summary of changes: gdb/ChangeLog | 9 +++++++++ gdb/config.in | 6 ++++++ gdb/configure | 26 ++++++++++++++++++++++++++ gdb/configure.ac | 5 +++++ gdb/guile/guile.c | 15 +++++++++++++++ 5 files changed, 61 insertions(+), 0 deletions(-) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-07-26 21:51 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-20 10:51 [Bug guile/17185] New: " dje at google dot com 2014-07-20 10:52 ` [Bug guile/17185] " dje at google dot com 2014-07-26 21:51 ` cvs-commit at gcc dot gnu.org [this message] 2014-07-27 3:36 ` cvs-commit at gcc dot gnu.org 2014-07-28 1:06 ` xdje42 at gmail dot com 2014-08-25 9:04 ` rosslagerwall at gmail dot com 2014-08-25 9:07 ` rosslagerwall at gmail dot com 2014-08-31 17:26 ` xdje42 at gmail dot com 2014-08-31 17:26 ` xdje42 at gmail dot com 2014-09-09 5:50 ` cvs-commit at gcc dot gnu.org 2014-09-10 4:47 ` cvs-commit at gcc dot gnu.org
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-17185-4717-J6yL96UBh4@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).