[debbugs-tracker] bug#24666: closed (converting srfi-18.test to standalone test case for debugging)

[GNU bug Tracking System]

Your message dated Wed, 01 Mar 2017 10:42:36 +0100
with message-id <address@hidden>
and subject line Re: bug#24666: converting srfi-18.test to standalone test case 
for debugging
has caused the debbugs.gnu.org bug report #24666,
regarding converting srfi-18.test to standalone test case for debugging
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
24666: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24666
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> 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
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#24666: converting srfi-18.test to standalone test case for debugging
>
>
>
>
> Date: 
>
> Wed, 01 Mar 2017 10:42:36 +0100
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)
>
>
>
>
> On Thu 20 Oct 2016 19:08, Jack Howarth <address@hidden> 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
>
>
> --- End Message ---