unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Linas Vepstas <linasvepstas@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: Now crashing [was Re: guile-2.9.2 and threading
Date: Wed, 7 Aug 2019 11:05:47 -0500	[thread overview]
Message-ID: <CAHrUA358CXm0834X+ZDOUVDyOMbcNWVCboam4_GY4fAAu1YkFQ@mail.gmail.com> (raw)
In-Reply-To: <87pnlj8ozv.fsf@netris.org>

[-- Attachment #1: Type: text/plain, Size: 623 bytes --]

I will ponder how to do that, it will take at least several weeks; I'll
file it through the normal guile bug report system. -- linas

On Mon, Aug 5, 2019 at 1:07 PM Mark H Weaver <mhw@netris.org> wrote:

> Hi Linas,
>
> Linas Vepstas <linasvepstas@gmail.com> writes:
> > However -- if one does call `scm_error` fairly rapidly, from multiple
> > threads, one will eventually hit a race condition and get a crash.
>
> If you could produce a small, self-contained example demonstrating this,
> it would enable us to investigate further.
>
>       Thanks,
>         Mark
>


-- 
cassette tapes - analog TV - film cameras - you

[-- Attachment #2: Type: text/html, Size: 1108 bytes --]

      reply	other threads:[~2019-08-07 16:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-02 23:25 guile-2.9.2 and threading Linas Vepstas
2019-06-07  4:26 ` Mark H Weaver
2019-06-07  5:01   ` Mark H Weaver
2019-07-09 20:46   ` Linas Vepstas
2019-07-14 21:59     ` Now crashing [was " Linas Vepstas
2019-07-14 22:03       ` Linas Vepstas
2019-07-15  3:03         ` Linas Vepstas
2019-07-17 16:27           ` Linas Vepstas
2019-07-17 17:47             ` Mark H Weaver
2019-07-17 21:44               ` Linas Vepstas
2019-07-18  1:42                 ` Linas Vepstas
2019-07-18  3:52                   ` Linas Vepstas
2019-07-21 21:10                     ` Linas Vepstas
2019-08-05 18:07                       ` Mark H Weaver
2019-08-07 16:05                         ` Linas Vepstas [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=CAHrUA358CXm0834X+ZDOUVDyOMbcNWVCboam4_GY4fAAu1YkFQ@mail.gmail.com \
    --to=linasvepstas@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=mhw@netris.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).