unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: xdje42@gmail.com,  gdb-patches@sourceware.org,  guile-user@gnu.org
Subject: Re: [PATCH] Improved ^c support for gdb/guile
Date: Mon, 17 Feb 2014 17:06:26 +0100	[thread overview]
Message-ID: <874n3xg1vh.fsf@gnu.org> (raw)
In-Reply-To: <201402170927.s1H9RgXf020012@glazunov.sibelius.xs4all.nl> (Mark	Kettenis's message of "Mon, 17 Feb 2014 10:27:42 +0100 (CET)")

Mark Kettenis <mark.kettenis@xs4all.nl> skribis:

> Didn't realize Guile used threads.  I guess that's safe if the
> interpreter makes sure it never calls into GDB code concurrently.

Actually :-), Guile comes with a REPL server, which clients (such as
Geiser, an Emacs mode for Scheme) can connect to.  But the server runs
in a separate thread.

My reaction as a Guiler was to spawn that server, and connect Emacs to
it so I could do live development “the usual way”.  But sometimes,
starting a new thread crashes GDB.  When it does not, accessing the
inferior’s memory from the server thread always fails (“Cannot access
memory”), even though accessing the same memory region from GDB’s main
thread does work.

Anyway, I gather that this is not supported.

(Note that by default, Guile 2.0 has one signal-handling thread in
addition to its main thread.  The BDW GC can also be configured to use a
separate marking thread.  I don’t think these are a concern for GDB
though.)

Thanks,
Ludo’.


      reply	other threads:[~2014-02-17 16:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-17  7:39 [PATCH] Improved ^c support for gdb/guile Doug Evans
2014-02-17  9:27 ` Mark Kettenis
2014-02-17 16:06   ` Ludovic Courtès [this message]

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874n3xg1vh.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=guile-user@gnu.org \
    --cc=mark.kettenis@xs4all.nl \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).