unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Linas Vepstas <linasvepstas@gmail.com>
Cc: 25238-done@debbugs.gnu.org
Subject: bug#25238: guile-2.2 threading bug
Date: Wed, 01 Mar 2017 15:42:31 +0100	[thread overview]
Message-ID: <87vartf488.fsf@pobox.com> (raw)
In-Reply-To: <CAHrUA34CEQtgvtVmT3y41YhfV_4LMqeZCUB8V0ojrgqwZyNWxQ@mail.gmail.com> (Linas Vepstas's message of "Tue, 20 Dec 2016 14:13:44 -0600")

On Tue 20 Dec 2016 21:13, Linas Vepstas <linasvepstas@gmail.com> writes:

> Thread 7 "a.out" received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7ffff3306700 (LWP 23578)]
> 0x00007ffff7b03076 in is_dynamic_state (x=0x0) at ../../libguile/fluids.c:97
> 97  return SCM_HAS_TYP7 (x, scm_tc7_dynamic_state);
> (gdb) bt
> #0  0x00007ffff7b03076 in is_dynamic_state (x=0x0) at ../../libguile/fluids.c:97
> #1  scm_set_current_dynamic_state (state=state@entry=0x0)
>     at ../../libguile/fluids.c:496
> #2  0x00007ffff7b6351a in guilify_self_2 (dynamic_state=dynamic_state@entry=0x0)
>     at ../../libguile/threads.c:466
> #3  0x00007ffff7b63e0c in scm_i_init_thread_for_guile (base=0x7ffff3305df0,
>     dynamic_state=0x0) at ../../libguile/threads.c:595
> #4  0x00007ffff7b63e59 in with_guile (base=base@entry=0x7ffff3305df0,
>     data=data@entry=0x7ffff3305e20) at ../../libguile/threads.c:638

I believe this one was fixed in 63bf6ffa0d3cdddf8151cc80ac18fe5dfb614587
which was released in 2.1.7.  Please open a new bug when you find
another one :)

Andy





      reply	other threads:[~2017-03-01 14:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-20 20:13 bug#25238: guile-2.2 threading bug Linas Vepstas
2017-03-01 14:42 ` Andy Wingo [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=87vartf488.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=25238-done@debbugs.gnu.org \
    --cc=linasvepstas@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).