Skip Menu |
 

This queue is for tickets about the Tk-Clock CPAN distribution.

Report information
The Basics
Id: 132669
Status: open
Priority: 0/
Queue: Tk-Clock

People
Owner: Nobody in particular
Requestors: ANDK [...] cpan.org
Cc: khw [...] cpan.org
SREZIC [...] cpan.org
AdminCc:

Bug Information
Severity: (no value)
Broken in: 0.41
Fixed in: (no value)



CC: SREZIC [...] cpan.org, KHW [...] cpan.org
Subject: Fails with Tk-804.035 when perl >= v5.27.8-307-g58e641fba5 and perl is built with -DDEBUGGING=both and -Dusethreads
Download (untitled) / with headers
text/plain 533b
In the subject line I try to express what I have observed on my smoker the last days. Plenty of fail reports can be found via the matrix at http://matrix.cpantesters.org/?dist=Tk-Clock+0.41 Just to pick an example: http://www.cpantesters.org/cpan/report/06c36a9e-9a65-11ea-9026-25288bde4a20 The typical error message produced: XS_Tk__Callback_Call error:panic: Mismatch between what Perl thinks LC_CTYPE is (en_US.UTF-8) and what internal glibc thinks (C) CC'd to SREZIC and KHW who can probably help diagnosing what's going on.
RT-Send-CC: khw [...] cpan.org, SREZIC [...] cpan.org
Download (untitled) / with headers
text/plain 1.6k
On Thu May 21 15:01:20 2020, ANDK wrote: Show quoted text
> In the subject line I try to express what I have observed on my smoker > the last days. > > Plenty of fail reports can be found via the matrix at > http://matrix.cpantesters.org/?dist=Tk-Clock+0.41 > > Just to pick an example: > http://www.cpantesters.org/cpan/report/06c36a9e-9a65-11ea-9026- > 25288bde4a20 > > The typical error message produced: > XS_Tk__Callback_Call error:panic: Mismatch between what Perl thinks > LC_CTYPE is (en_US.UTF-8) and what internal glibc thinks (C) > > CC'd to SREZIC and KHW who can probably help diagnosing what's going > on.
Some relevant commits to the Perl 5 core distribution: ##### commit 58e641fba50d93bcd84c0dc042b36d201958293d Author: Karl Williamson <khw@cpan.org> AuthorDate: Thu Feb 15 22:44:24 2018 -0700 Commit: Karl Williamson <khw@cpan.org> CommitDate: Sun Feb 18 15:44:23 2018 -0700 Add switch_to_globale_locale() This new API function is for use in applications that call alien library routines that are expecting the old pre-POSIX 2008 locale functionality, namely a single global locale accessible via setlocale(). This function converts the calling thread to use that global locale, if not already there. ##### ##### commit e9bc6d6b34afc0063cc5181b59f77eeb81b1182d Author: Karl Williamson <khw@cpan.org> AuthorDate: Mon Feb 5 22:11:51 2018 -0700 Commit: Karl Williamson <khw@cpan.org> CommitDate: Sun Feb 18 15:44:23 2018 -0700 Add thread-safe locale handling This (large) commit allows locales to be used in threaded perls on platforms that support it. This includes recent Windows and Posix 2008 ones. #####
Download (untitled) / with headers
text/plain 1.9k
On Thu May 21 15:01:20 2020, ANDK wrote: Show quoted text
> In the subject line I try to express what I have observed on my smoker > the last days. > > Plenty of fail reports can be found via the matrix at > http://matrix.cpantesters.org/?dist=Tk-Clock+0.41 > > Just to pick an example: > http://www.cpantesters.org/cpan/report/06c36a9e-9a65-11ea-9026- > 25288bde4a20 > > The typical error message produced: > XS_Tk__Callback_Call error:panic: Mismatch between what Perl thinks > LC_CTYPE is (en_US.UTF-8) and what internal glibc thinks (C) > > CC'd to SREZIC and KHW who can probably help diagnosing what's going > on.
1. If you omit "-Duselongdouble" from config_args, do you still get these test failures? 2. I notice that you have two separate reports for the same commit, which differ in only one config_arg and in their result: ##### http://www.cpantesters.org/cpan/report/89787af0-9a66-11ea-9610-d84d8bde4a20 44523d1ffde5f23de2e13216cdbac46357631904 config_args='-Dprefix=/home/sand/src/perl/repoperls/installed-perls/host/k93msid/v5.30.0/8854 -Dmyhostname=k93msid -Dinstallusrbinperl=n -Uversiononly -Dusedevel -des -Ui_db -Dlibswanted=cl pthread socket inet nsl gdbm dbm malloc dl ld sun m crypt sec util c cposix posix ucb BSD gdbm_compat -Duseithreads -Duselongdouble -DEBUGGING=-g' Result: PASS http://www.cpantesters.org/cpan/report/da9ac352-9b60-11ea-8e9a-483afa4822e2 44523d1ffde5f23de2e13216cdbac46357631904 config_args='-Dprefix=/home/sand/src/perl/repoperls/installed-perls/host/k93msid/v5.30.0/29fb -Dmyhostname=k93msid -Dinstallusrbinperl=n -Uversiononly -Dusedevel -des -Ui_db -Dlibswanted=cl pthread socket inet nsl gdbm dbm malloc dl ld sun m crypt sec util c cposix posix ucb BSD gdbm_compat -Duseithreads -Uuselongdouble -DEBUGGING=both' Result: FAIL ##### a. Am I reading this correctly? b. On other test reports, is the difference between PASS and FAIL the difference between '-DEBUGGING=-g' and '-DEBUGGING=both'? Thank you very much. Jim Keenan
Download (untitled) / with headers
text/plain 1.2k
On Thu May 21 15:01:20 2020, ANDK wrote: Show quoted text
> In the subject line I try to express what I have observed on my smoker > the last days. > > Plenty of fail reports can be found via the matrix at > http://matrix.cpantesters.org/?dist=Tk-Clock+0.41 > > Just to pick an example: > http://www.cpantesters.org/cpan/report/06c36a9e-9a65-11ea-9026- > 25288bde4a20 > > The typical error message produced: > XS_Tk__Callback_Call error:panic: Mismatch between what Perl thinks > LC_CTYPE is (en_US.UTF-8) and what internal glibc thinks (C) > > CC'd to SREZIC and KHW who can probably help diagnosing what's going > on.
I can confirm the test failures when Tk-Clock is tested against perl 5 blead built with threads, longdouble and -DEBUGGING=both. See attachment. Building with the same configuration except -DEBUGGING=-g PASSes. I notice that https://metacpan.org/release/Tk-Clock suggests that the latest version of Tk-Clock, 0.41, was uploaded very recently on April 09 2020. This may explain why the failures on Andreas's machines have only begun to appear recently. However, in the git checkout there is no tag later than 'v0.39' and the most recent CommitDate is Thu Oct 31 06:07:34 2019. So I'm confused as to how to proceed. Thank you very much. Jim Keenan
Subject: rtc-132669-tk-clock-debugging-both.txt
$ bleadperl -v | head -2 | tail -1 This is perl 5, version 31, subversion 12 (v5.31.12 (v5.31.11-37-gd7600dcd5c)) built for x86_64-linux-thread-multi-ld $ bleadperl -V:config_args config_args='-des -Dusedevel -Dusethreads -Duselongdouble -DEBUGGING=both -Dprefix=/home/jkeenan/testing/blead -Uversiononly -Dman1dir=none -Dman3dir=none'; $ bleadprove -vb t/*.t t/00_pod.t ....... 1..0 # SKIP Test::Pod 1.00 required for testing POD skipped: Test::Pod 1.00 required for testing POD t/01_pod.t ....... 1..0 # SKIP Test::Pod::Covarage required for testing POD Coverage skipped: Test::Pod::Covarage required for testing POD Coverage t/10_base.t ...... ok 1 - use Tk; ok 2 - use Tk::Clock; ok 3 - Clock Widget ok 4 - Month format m Jan in C ok 5 - Month format mm Mar in C ok 6 - Month format mmm May in C ok 7 - Month format mmmm Jul in C ok 8 - Weekday format ddd Sun in C ok 9 - Weekday format dddd Tue in C ok 10 - Month format m Jan in en_US.UTF-8 ok 11 - Month format mm Mar in en_US.UTF-8 ok 12 - Month format mmm May in en_US.UTF-8 ok 13 - Month format mmmm Jul in en_US.UTF-8 ok 14 - Weekday format ddd Sun in en_US.UTF-8 ok 15 - Weekday format dddd Tue in en_US.UTF-8 ok 16 - config ok 17 - pack ok 18 - Delay is 0 ok 19 - Period is 5000 ok 20 - First after 5000 ok 21 - Blue4 Ad Yellow ok 22 - Tan4 aD ok 23 - Maroon4 AD m/d/y hh:MM A ok 24 - Red4 aD mmm yyy HH:MM:SS ok 25 - Gray10 right digital ok 26 - Gray30 left digital ok 27 - Purple4 aD dddd\nd mmm yyy '' ok 28 - Gray75 Ad scale 300 ok 29 - Ad scale 67 tickFreq 5 ok 30 - AD scale 100 tickFreq 5 ww dd-mm dd HH:SS ok 31 - Increase date font size ok 32 - Station clock: hand centers and tick width ok 33 - Station clock: Time offset -4'05:06:07 ok 34 - Destroy Clock XS_Tk__Callback_Call error:panic: Mismatch between what Perl thinks LC_CTYPE is (en_US.UTF-8) and what internal glibc thinks (C) # Tests were run but no plan was declared and done_testing() was not seen. Dubious, test returned 254 (wstat 65024, 0xfe00) All 34 subtests passed t/20_resize.t .... ok 1 - use Tk; ok 2 - use Tk::Clock; ok 3 - Clock Widget ok 4 - config ok 5 - pack # Feel free to resize the clock now with your mouse! ok 6 - Destroy Clock ok 7 - Destroy Main ok 8 - no warnings 1..8 ok t/30_dual.t ...... ok 1 - use Tk; ok 2 - use Tk::Clock; ok 3 - Clock Local TimeZone ok 4 - config ok 5 - grid ok 6 - Clock GMT ok 7 - config ok 8 - grid ok 9 - Clock MET-1METDST ok 10 - config ok 11 - grid ok 12 - Clock Tokyo ok 13 - config ok 14 - grid ok 15 - Destroy Clock ok 16 - Destroy Clock ok 17 - Destroy Clock ok 18 - Destroy Clock XS_Tk__Callback_Call error:panic: Mismatch between what Perl thinks LC_CTYPE is (en_US.UTF-8) and what internal glibc thinks (C) # Tests were run but no plan was declared and done_testing() was not seen. Dubious, test returned 254 (wstat 65024, 0xfe00) All 18 subtests passed t/40_backdrop.t .. ok 1 - use Tk; ok 2 - use Tk::Photo; ok 3 - use Tk::Clock; ok 4 - base clock ok 5 - Photo 1 ok 6 - Photo 2 ok 7 - config () ok 8 - pack ok 9 - no warnings 1..9 ok Test Summary Report ------------------- t/10_base.t (Wstat: 65024 Tests: 34 Failed: 0) Non-zero exit status: 254 Parse errors: No plan found in TAP output t/30_dual.t (Wstat: 65024 Tests: 18 Failed: 0) Non-zero exit status: 254 Parse errors: No plan found in TAP output Files=6, Tests=69, 117 wallclock secs ( 0.06 usr 0.01 sys + 1.28 cusr 0.12 csys = 1.47 CPU) Result: FAIL
Download (untitled) / with headers
text/plain 2.5k
On Thu May 21 17:06:51 2020, JKEENAN wrote: Show quoted text
> On Thu May 21 15:01:20 2020, ANDK wrote:
> > In the subject line I try to express what I have observed on my > > smoker > > the last days. > > > > Plenty of fail reports can be found via the matrix at > > http://matrix.cpantesters.org/?dist=Tk-Clock+0.41 > > > > Just to pick an example: > > http://www.cpantesters.org/cpan/report/06c36a9e-9a65-11ea-9026- > > 25288bde4a20 > > > > The typical error message produced: > > XS_Tk__Callback_Call error:panic: Mismatch between what Perl thinks > > LC_CTYPE is (en_US.UTF-8) and what internal glibc thinks (C) > > > > CC'd to SREZIC and KHW who can probably help diagnosing what's going > > on.
> > I can confirm the test failures when Tk-Clock is tested against perl 5 > blead built with threads, longdouble and -DEBUGGING=both. See > attachment. Building with the same configuration except -DEBUGGING=-g > PASSes. > > I notice that https://metacpan.org/release/Tk-Clock suggests that the > latest version of Tk-Clock, 0.41, was uploaded very recently on April > 09 2020. This may explain why the failures on Andreas's machines have > only begun to appear recently. However, in the git checkout there is > no tag later than 'v0.39' and the most recent CommitDate is Thu Oct 31 > 06:07:34 2019. So I'm confused as to how to proceed. > > Thank you very much. > Jim Keenan
To further muddy the waters ... When I build Perl 5 blead with threads, longdouble but '-DEBUGGING=-g' and test an *earlier* version of Tk-Clock, I get a PASS. ##### $ thisperl -V:config_args config_args='-des -Dusedevel -Dusethreads -Duselongdouble -DEBUGGING=-g -Dprefix=/home/jkeenan/testing/56d9fe2f0976a30544c45bec229c1199e2e95396 -Uversiononly -Dman1dir=none -Dman3dir=none'; $ gitshowf commit fb41f1c902c1cf1ae5c1a2077162d4c231fe217c (HEAD, tag: v0.36) Author: H.Merijn Brand - Tux <h.m.brand@xs4all.nl> AuthorDate: Fri Apr 11 08:05:12 2014 +0200 Commit: H.Merijn Brand - Tux <h.m.brand@xs4all.nl> CommitDate: Fri Apr 11 08:05:12 2014 +0200 Deal with single-digit formats with dynamic width ... $ thisprove -b t/10_base.t t/30_dual.t t/10_base.t .. ok t/30_dual.t .. ok All tests successful. Files=2, Tests=56, 96 wallclock secs ( 0.03 usr 0.01 sys + 0.66 cusr 0.05 csys = 0.75 CPU) Result: PASS ##### However, if I build with -DEBUGGING=both and then test Tk-Clock at v0.36, I get the failures reported previously. So my hunch is that the recent CPAN upload of v0.41 of Tk-Clock triggered CPANtesters runs which are disclosing some problem with '-DEBUGGING=both' versus '-DEBUGGING=-g'. Thank you very much. Jim Keenan
RT-Send-CC: khw [...] cpan.org, SREZIC [...] cpan.org
Download (untitled) / with headers
text/plain 3.5k
On Thu May 21 17:27:45 2020, JKEENAN wrote: Show quoted text
> On Thu May 21 17:06:51 2020, JKEENAN wrote:
> > On Thu May 21 15:01:20 2020, ANDK wrote:
> > > In the subject line I try to express what I have observed on my > > > smoker > > > the last days. > > > > > > Plenty of fail reports can be found via the matrix at > > > http://matrix.cpantesters.org/?dist=Tk-Clock+0.41 > > > > > > Just to pick an example: > > > http://www.cpantesters.org/cpan/report/06c36a9e-9a65-11ea-9026- > > > 25288bde4a20 > > > > > > The typical error message produced: > > > XS_Tk__Callback_Call error:panic: Mismatch between what Perl thinks > > > LC_CTYPE is (en_US.UTF-8) and what internal glibc thinks (C) > > > > > > CC'd to SREZIC and KHW who can probably help diagnosing what's > > > going > > > on.
> > > > I can confirm the test failures when Tk-Clock is tested against perl > > 5 > > blead built with threads, longdouble and -DEBUGGING=both. See > > attachment. Building with the same configuration except -DEBUGGING=- > > g > > PASSes. > > > > I notice that https://metacpan.org/release/Tk-Clock suggests that the > > latest version of Tk-Clock, 0.41, was uploaded very recently on April > > 09 2020. This may explain why the failures on Andreas's machines > > have > > only begun to appear recently. However, in the git checkout there is > > no tag later than 'v0.39' and the most recent CommitDate is Thu Oct > > 31 > > 06:07:34 2019. So I'm confused as to how to proceed. > > > > Thank you very much. > > Jim Keenan
> > To further muddy the waters ... > > When I build Perl 5 blead with threads, longdouble but '-DEBUGGING=-g' > and test an *earlier* version of Tk-Clock, I get a PASS. > > ##### > $ thisperl -V:config_args > config_args='-des -Dusedevel -Dusethreads -Duselongdouble -DEBUGGING=- > g > -Dprefix=/home/jkeenan/testing/56d9fe2f0976a30544c45bec229c1199e2e95396 > -Uversiononly -Dman1dir=none -Dman3dir=none'; > > $ gitshowf > commit fb41f1c902c1cf1ae5c1a2077162d4c231fe217c (HEAD, tag: v0.36) > Author: H.Merijn Brand - Tux <h.m.brand@xs4all.nl> > AuthorDate: Fri Apr 11 08:05:12 2014 +0200 > Commit: H.Merijn Brand - Tux <h.m.brand@xs4all.nl> > CommitDate: Fri Apr 11 08:05:12 2014 +0200 > > Deal with single-digit formats with dynamic width > ... > > $ thisprove -b t/10_base.t t/30_dual.t > t/10_base.t .. ok > t/30_dual.t .. ok > All tests successful. > Files=2, Tests=56, 96 wallclock secs ( 0.03 usr 0.01 sys + 0.66 cusr > 0.05 csys = 0.75 CPU) > Result: PASS > ##### > > However, if I build with -DEBUGGING=both and then test Tk-Clock at > v0.36, I get the failures reported previously. > > So my hunch is that the recent CPAN upload of v0.41 of Tk-Clock > triggered CPANtesters runs which are disclosing some problem with '- > DEBUGGING=both' versus '-DEBUGGING=-g'. > > Thank you very much. > Jim Keenan
Further debugging suggests: 1. '-Duselongdouble' is not responsible for the test failures. Deleting it from config_args does not affect the Tk-Clock tests' results. ('-Duselongdouble' does, however, appear to cause Tk's test suite to hang indefinitely at t/errordialog.t *when run via cpanm*. But that's for another ticket in a different queue.) 2. '-Dusethreads' is implicated in the test failures. When I build a perl at blead with '-DEBUGGING=both' but *without* '-Duseithreads', Tk-Clock tests PASS at both tag v0.36 and at HEAD. I'm leaning to the hypothesis is that this is a bug in perl 5 blead when built with '-DEBUGGING=both -Dusethreads'. It would be good if we could reduce the test failures in Tk-Clock's test suite to debug this further and perhaps bisect it. Thank you very much. Jim Keenan
RT-Send-CC: SREZIC [...] cpan.org, khw [...] cpan.org
Download (untitled) / with headers
text/plain 4.8k
On Thu May 21 18:30:31 2020, JKEENAN wrote: Show quoted text
> On Thu May 21 17:27:45 2020, JKEENAN wrote:
> > On Thu May 21 17:06:51 2020, JKEENAN wrote:
> > > On Thu May 21 15:01:20 2020, ANDK wrote:
> > > > In the subject line I try to express what I have observed on my > > > > smoker > > > > the last days. > > > > > > > > Plenty of fail reports can be found via the matrix at > > > > http://matrix.cpantesters.org/?dist=Tk-Clock+0.41 > > > > > > > > Just to pick an example: > > > > http://www.cpantesters.org/cpan/report/06c36a9e-9a65-11ea-9026- > > > > 25288bde4a20 > > > > > > > > The typical error message produced: > > > > XS_Tk__Callback_Call error:panic: Mismatch between what Perl > > > > thinks > > > > LC_CTYPE is (en_US.UTF-8) and what internal glibc thinks (C) > > > > > > > > CC'd to SREZIC and KHW who can probably help diagnosing what's > > > > going > > > > on.
> > > > > > I can confirm the test failures when Tk-Clock is tested against > > > perl > > > 5 > > > blead built with threads, longdouble and -DEBUGGING=both. See > > > attachment. Building with the same configuration except > > > -DEBUGGING=- > > > g > > > PASSes. > > > > > > I notice that https://metacpan.org/release/Tk-Clock suggests that > > > the > > > latest version of Tk-Clock, 0.41, was uploaded very recently on > > > April > > > 09 2020. This may explain why the failures on Andreas's machines > > > have > > > only begun to appear recently. However, in the git checkout there > > > is > > > no tag later than 'v0.39' and the most recent CommitDate is Thu Oct > > > 31 > > > 06:07:34 2019. So I'm confused as to how to proceed. > > > > > > Thank you very much. > > > Jim Keenan
> > > > To further muddy the waters ... > > > > When I build Perl 5 blead with threads, longdouble but '-DEBUGGING=- > > g' > > and test an *earlier* version of Tk-Clock, I get a PASS. > > > > ##### > > $ thisperl -V:config_args > > config_args='-des -Dusedevel -Dusethreads -Duselongdouble > > -DEBUGGING=- > > g > > -Dprefix=/home/jkeenan/testing/56d9fe2f0976a30544c45bec229c1199e2e95396 > > -Uversiononly -Dman1dir=none -Dman3dir=none'; > > > > $ gitshowf > > commit fb41f1c902c1cf1ae5c1a2077162d4c231fe217c (HEAD, tag: v0.36) > > Author: H.Merijn Brand - Tux <h.m.brand@xs4all.nl> > > AuthorDate: Fri Apr 11 08:05:12 2014 +0200 > > Commit: H.Merijn Brand - Tux <h.m.brand@xs4all.nl> > > CommitDate: Fri Apr 11 08:05:12 2014 +0200 > > > > Deal with single-digit formats with dynamic width > > ... > > > > $ thisprove -b t/10_base.t t/30_dual.t > > t/10_base.t .. ok > > t/30_dual.t .. ok > > All tests successful. > > Files=2, Tests=56, 96 wallclock secs ( 0.03 usr 0.01 sys + 0.66 > > cusr > > 0.05 csys = 0.75 CPU) > > Result: PASS > > ##### > > > > However, if I build with -DEBUGGING=both and then test Tk-Clock at > > v0.36, I get the failures reported previously. > > > > So my hunch is that the recent CPAN upload of v0.41 of Tk-Clock > > triggered CPANtesters runs which are disclosing some problem with '- > > DEBUGGING=both' versus '-DEBUGGING=-g'. > > > > Thank you very much. > > Jim Keenan
> > Further debugging suggests: > > 1. '-Duselongdouble' is not responsible for the test failures. > Deleting it from config_args does not affect the Tk-Clock tests' > results. ('-Duselongdouble' does, however, appear to cause Tk's test > suite to hang indefinitely at t/errordialog.t *when run via cpanm*. > But that's for another ticket in a different queue.) > > 2. '-Dusethreads' is implicated in the test failures. When I build a > perl at blead with '-DEBUGGING=both' but *without* '-Duseithreads', > Tk-Clock tests PASS at both tag v0.36 and at HEAD. > > I'm leaning to the hypothesis is that this is a bug in perl 5 blead > when built with '-DEBUGGING=both -Dusethreads'. It would be good if > we could reduce the test failures in Tk-Clock's test suite to debug > this further and perhaps bisect it. > > Thank you very much. > Jim Keenan
The tests fail in blocks that use the ja_JP.utf8 locale. If I comment out the unit tests in t/10 and t/30 that use this locale, the tests PASS on a perl-5.28 or later built with -Dusethreads and -DEBUGGING=both. This problem can also be seen when the attached program is run by that kind of perl. My belief now is that this is a case where Tk-Clock (or, perhaps, Tk) needs to be updated to reflect the changes in perl made in this commit: ##### commit 58e641fba50d93bcd84c0dc042b36d201958293d Author: Karl Williamson <khw@cpan.org> AuthorDate: Thu Feb 15 22:44:24 2018 -0700 Commit: Karl Williamson <khw@cpan.org> CommitDate: Sun Feb 18 15:44:23 2018 -0700 Add switch_to_globale_locale() This new API function is for use in applications that call alien library routines that are expecting the old pre-POSIX 2008 locale functionality, namely a single global locale accessible via setlocale(). This function converts the calling thread to use that global locale, if not already there. ##### Thank you very much. Jim Keenan
Subject: gh-17797-clock.pl
Download gh-17797-clock.pl
text/x-perl 1.2k
use strict; use warnings; use Tk; use Tk::Clock; END { print "Finished!\n"; } my $rv; my ($delay, $period, $m, $c) = (0, 300); unless ($m = eval { MainWindow->new (-title => "clock") }) { exit 0; } $c = $m->Clock (-background => "Black"); print "Clock Widget ", (defined $c ? "defined" : "not defined"), "\n"; print "Delay is 0 ", ($delay == 0 ? "ok" : "not ok"), "\n"; print "Period is $period ", (($period =~ qr/^\d+$/) ? "ok" : "not ok"), "\n"; $delay += $period; print "First after $delay ", (($delay =~ qr/^\d+$/) ? "ok" : "not ok"), "\n"; $delay += $period; $c->after ($delay, sub { $c->configure (-background => "Purple4"); $rv = $c->config ({ useAnalog => 0, useInfo => 0, useDigital => 1, useLocale => ($^O eq "MSWin32" ? "Japanese_Japan.932" : "ja_JP.utf8"), timeFont => "Helvetica 8", dateFont => "Helvetica 8", dateFormat => "dddd\nd mmm yyy", timeFormat => "", }); print "Purple4 aD dddd\\nd mmm yyy '' ", ($rv ? "ok" : "not ok"), "\n"; }); $delay += $period; $c->after ($delay, sub { print "XXX: Entering destructors\n"; $c->destroy; print "Destroy Clock ", (!Exists ($c) ? "ok" : "not ok"), "\n"; local $@; eval {$m->destroy; }; $@ and warn "Destroy Main FAIL: $@"; }); MainLoop;
CC: SREZIC [...] cpan.org
Subject: Re: [rt.cpan.org #132669] Fails with Tk-804.035 when perl >= v5.27.8-307-g58e641fba5 and perl is built with -DDEBUGGING=both and -Dusethreads
Date: Sat, 23 May 2020 17:18:28 -0600
To: bug-Tk-Clock [...] rt.cpan.org, ANDK [...] cpan.org
From: Karl Williamson <khw [...] cpan.org>
Download (untitled) / with headers
text/plain 603b
On 5/23/20 12:21 PM, James E Keenan via RT wrote: Show quoted text
> My belief now is that this is a case where Tk-Clock (or, perhaps, Tk) needs to be updated to reflect the changes in perl made in this commit:
I haven't looked at the module, but Jim is likely to right. The docs outline the issues involved. There are three functions likely to be of use sync_locale switch_to_global_locale Perl_setlocale The first two are ported all the way back by Devel::PPPort; the final one is available only as of 5.27.2. I had started to port it back, and could resume working on it if it would be useful in this case.
RT-Send-CC: khw [...] cpan.org, SREZIC [...] cpan.org
Download (untitled) / with headers
text/plain 809b
On Sat May 23 19:19:35 2020, khw wrote: Show quoted text
> On 5/23/20 12:21 PM, James E Keenan via RT wrote:
> > My belief now is that this is a case where Tk-Clock (or, perhaps, Tk) > > needs to be updated to reflect the changes in perl made in this > > commit:
> > I haven't looked at the module, but Jim is likely to right. The docs > outline the issues involved. There are three functions likely to be > of use > > sync_locale > switch_to_global_locale > Perl_setlocale
The code at hand only uses 137: my $curloc = POSIX::setlocale (POSIX::LC_TIME (), "") || "C"; 138: my $newloc = POSIX::setlocale (POSIX::LC_TIME (), $locale) || "C"; 154: POSIX::setlocale (POSIX::LC_TIME (), $curloc); (re)reading this ticket twice still gives me no hints to where what shopuld/could be changed to fix this issue.
CC: SREZIC [...] cpan.org
Subject: Re: [rt.cpan.org #132669] Fails with Tk-804.035 when perl >= v5.27.8-307-g58e641fba5 and perl is built with -DDEBUGGING=both and -Dusethreads
Date: Tue, 2 Jun 2020 09:21:02 -0600
To: bug-Tk-Clock [...] rt.cpan.org
From: Karl Williamson <khw [...] cpan.org>
On 6/2/20 2:58 AM, H.Merijn Brand via RT wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=132669 > > > On Sat May 23 19:19:35 2020, khw wrote:
>> On 5/23/20 12:21 PM, James E Keenan via RT wrote:
>>> My belief now is that this is a case where Tk-Clock (or, perhaps, Tk) >>> needs to be updated to reflect the changes in perl made in this >>> commit:
>> >> I haven't looked at the module, but Jim is likely to right. The docs >> outline the issues involved. There are three functions likely to be >> of use >> >> sync_locale >> switch_to_global_locale >> Perl_setlocale
> > The code at hand only uses > > 137: my $curloc = POSIX::setlocale (POSIX::LC_TIME (), "") || "C"; > 138: my $newloc = POSIX::setlocale (POSIX::LC_TIME (), $locale) || "C"; > 154: POSIX::setlocale (POSIX::LC_TIME (), $curloc); > > (re)reading this ticket twice still gives me no hints to where what shopuld/could be changed to fix this issue. >
The function I mentioned are from C code. If this module isn't using XS, then it's not the module's fault. I'll have to investigate


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.