From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: xdje42@gmail.com
Cc: gdb-patches@sourceware.org, guile-user@gnu.org, ludo@gnu.org
Subject: Re: [PATCH] Improved ^c support for gdb/guile
Date: Mon, 17 Feb 2014 09:27:00 -0000 [thread overview]
Message-ID: <201402170927.s1H9RgXf020012@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <wrbvbwejihe.fsf@sspiff.org> (message from Doug Evans on Mon, 17 Feb 2014 02:39:25 -0500)
> From: Doug Evans <xdje42@gmail.com>
> Date: Mon, 17 Feb 2014 02:39:25 -0500
>
> Hi.
>
> Here's my modest contribution to the Guile anniversary potluck.
>
> The patch to selftest-support.exp could be done differently,
> I've tried to keep it simple. The problem is that gdb with guile
> will get SIGPWR from time to time when Guile's GC kicks in,
> and we need this to not alter test behaviour. The patch just
> tells the parent gdb to ignore SIGPWR, which is simple enough
> without loss of coverage. A good question is what other signals
> Guile GC might use.
SIGPWR? Doesn't exist on *BSD. Guess it uses some other random
signal there?
Didn't realize Guile used threads. I guess that's safe if the
interpreter makes sure it never calls into GDB code concurrently. But
it does make debugging GDB harder. And I hope this is not an excuse
for other people to start using threads in other bits of GDB.
next prev parent reply other threads:[~2014-02-17 9:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 7:39 Doug Evans
2014-02-17 9:27 ` Mark Kettenis [this message]
2014-02-17 16:06 ` Ludovic Courtès
2014-02-17 20:26 ` [PATCH v2] " Doug Evans
2014-02-17 20:43 ` Eli Zaretskii
2014-02-17 20:59 ` Doug Evans
2014-02-17 21:13 ` Eli Zaretskii
2014-02-18 0:37 ` Doug Evans
2014-02-18 11:20 ` Ludovic Courtès
2014-02-18 16:02 ` Eli Zaretskii
2014-02-18 16:45 ` Ludovic Courtès
2014-02-18 16:56 ` Eli Zaretskii
2014-02-18 17:46 ` Ludovic Courtès
2014-02-18 17:58 ` Eli Zaretskii
2014-02-18 23:08 ` Ludovic Courtès
2014-02-19 7:51 ` Mark H Weaver
2014-02-19 16:42 ` Eli Zaretskii
2014-02-18 17:31 ` Doug Evans
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=201402170927.s1H9RgXf020012@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=guile-user@gnu.org \
--cc=ludo@gnu.org \
--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