GNU bug report logs - #24666
converting srfi-18.test to standalone test case for debugging

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 24666 in the body.
You can then email your comments to 24666 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jack Howarth <howarth.mailing.lists <at> gmail.com>
To: bug-guile <at> gnu.org
Subject: converting srfi-18.test to standalone test case for debugging
Date: Tue, 11 Oct 2016 08:55:06 -0400

    Does anyone know how to convert the srfi-18.test test case into a
standalone one that can be debugged in lldb or gdb? On darwin15, I
have confirmed that the thread-local-storage support is causing the
failures of...

 FAIL: srfi-18.test: thread-terminate!: termination destroys non-started thread
 FAIL: srfi-18.test: thread-terminate!: termination destroys started thread

and that passing configure 'ac_cv_have_thread_storage_class=no' to
configure when building guile 2.0.12 suppresses these failures.
   I've opened a radar bug report with Apple, radar:// 2868809 "guile
2.0.12 exposes potential thread-local-storage bug on Mac OS X", but
still need to add a stand-alone test case derived from srfi-18.test
that can be debugged in lldb.
            Jack

Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jack Howarth <howarth.mailing.lists <at> gmail.com>
To: bug-guile <at> gnu.org
Subject: Re: converting srfi-18.test to standalone test case for debugging
Date: Thu, 20 Oct 2016 13:08:07 -0400

I finally puzzled out how to run the srfi-18.test failing test case as
a stand alone one with...

cd /opt/local/var/macports/build/_Users_howarth_ports_lang_guile/guile/work/guile-2.0.13/test-suite
setenv GUILE_LOAD_PATH
/opt/local/var/macports/build/_Users_howarth_ports_lang_guile/guile/work/guile-2.0.13/test-suite
setenv TEST_SUITE_DIR
/opt/local/var/macports/build/_Users_howarth_ports_lang_guile/guile/work/guile-2.0.13/test-suite/tests
/opt/local/bin/guile  -e main -s guile-test srfi-18.test

Running srfi-18.test
FAIL: srfi-18.test: thread-terminate!: termination destroys non-started thread
FAIL: srfi-18.test: thread-terminate!: termination destroys started thread

Totals for this test run:
passes:                 59
failures:               2
unexpected passes:      0
expected failures:      0
unresolved test cases:  0
untested test cases:    0
unsupported test cases: 0
errors:                 0

While the comments in guile-test mentioned the requirement for setting
TEST_SUITE_DIR, it is missing any discussion of the need to set
GUILE_LOAD_PATH as well. That should be added.

On Tue, Oct 11, 2016 at 8:55 AM, Jack Howarth
<howarth.mailing.lists <at> gmail.com> wrote:
>     Does anyone know how to convert the srfi-18.test test case into a
> standalone one that can be debugged in lldb or gdb? On darwin15, I
> have confirmed that the thread-local-storage support is causing the
> failures of...
>
>  FAIL: srfi-18.test: thread-terminate!: termination destroys non-started thread
>  FAIL: srfi-18.test: thread-terminate!: termination destroys started thread
>
> and that passing configure 'ac_cv_have_thread_storage_class=no' to
> configure when building guile 2.0.12 suppresses these failures.
>    I've opened a radar bug report with Apple, radar:// 2868809 "guile
> 2.0.12 exposes potential thread-local-storage bug on Mac OS X", but
> still need to add a stand-alone test case derived from srfi-18.test
> that can be debugged in lldb.
>             Jack

Message #13 received at 24666-done <at> debbugs.gnu.org (full text, mbox):

From: Andy Wingo <wingo <at> pobox.com>
To: Jack Howarth <howarth.mailing.lists <at> gmail.com>
Cc: 24666-done <at> debbugs.gnu.org
Subject: Re: bug#24666: converting srfi-18.test to standalone test case for
 debugging
Date: Wed, 01 Mar 2017 10:42:36 +0100

On Thu 20 Oct 2016 19:08, Jack Howarth <howarth.mailing.lists <at> gmail.com> writes:

> I finally puzzled out how to run the srfi-18.test failing test case as
> a stand alone one with...
>
> cd /opt/local/var/macports/build/_Users_howarth_ports_lang_guile/guile/work/guile-2.0.13/test-suite
> setenv GUILE_LOAD_PATH
> /opt/local/var/macports/build/_Users_howarth_ports_lang_guile/guile/work/guile-2.0.13/test-suite
> setenv TEST_SUITE_DIR
> /opt/local/var/macports/build/_Users_howarth_ports_lang_guile/guile/work/guile-2.0.13/test-suite/tests
> /opt/local/bin/guile  -e main -s guile-test srfi-18.test
>
> Running srfi-18.test
> FAIL: srfi-18.test: thread-terminate!: termination destroys non-started thread
> FAIL: srfi-18.test: thread-terminate!: termination destroys started thread
>
> Totals for this test run:
> passes:                 59
> failures:               2
> unexpected passes:      0
> expected failures:      0
> unresolved test cases:  0
> untested test cases:    0
> unsupported test cases: 0
> errors:                 0
>
> While the comments in guile-test mentioned the requirement for setting
> TEST_SUITE_DIR, it is missing any discussion of the need to set
> GUILE_LOAD_PATH as well. That should be added.

Thanks for tracking this one down.  I usually only run "./check-guile
srfi-18.test"; I never looked seriously into this file.  There's a bit
of a mess here and elsewhere in the test suite about modules and paths,
but I did add a comment.

FYI in the upcoming Guile 2.2 (and already in the prereleases),
thread-terminate! should be much more reliable.

Andy

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.