New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
perl 5.14.2 test suite failures on x86_64-sun-solaris2.10 #11681
Comments
From @jkeenanOn Fri Sep 30 14:29:35 2011, Tim.Mooney@ndsu.edu wrote:
The original post included the full output of 't/harness', which was too Let me try to boil it down.
[snip] Let's go to one of the first block of test failures. [snip]
[snip]
[snip]
[snip]
[snip]
[snip]
Would it be possible to provide more verbose output on these particular Thank you very much. |
The RT System itself - Status changed from 'new' to 'open' |
From Tim.Mooney@ndsu.edu
Jim, et. al.- When I've used rt in the past, reply-via-email has "just worked". I've Is perlbug's RT not using reply-via-email, or is there a significant Thanks, Tim |
From @jkeenanOn Tue Apr 17 13:38:12 2012, enchanter wrote:
I have to admit that I'm not familiar with reply-via-email, so I suspect I know that the web interface works, because that's what I use. If you Thank you very much. |
From Tim.Mooney@ndsu.eduIn regard to: [perl #100450] perl 5.14.2 test suite failures on...:
Thanks James, and sorry for the delay in responding.
Sounds good.
01:22 PM dogbert t$./perl -I ../lib re/regexp_qr_embed_thr.t 01:23 PM dogbert t$dbx perl core
01:24 PM dogbert t$./perl op/getpid.t 01:25 PM dogbert t$dbx perl core
01:30 PM dogbert t$./perl -I ../lib op/gv.t
01:33 PM dogbert t$./perl -I ../lib op/reset.t 01:34 PM dogbert t$dbx perl core So, that seems to be the common issue; all of the failures are coming I can provide additional info for any of the other tests you asked about, I'll send email again when I'm able to get dbx to actually show me the Tim |
From Tim.Mooney@ndsu.eduIn regard to: [perl #100450] perl 5.14.2 test suite failures on...:
So I recompiled with both optimization and debugging, and now I can get 02:28 PM dogbert perl-5.14.2$t/perl -I lib t/op/getpid.t 02:28 PM dogbert perl-5.14.2$cd t/ 02:29 PM dogbert t$dbx perl core (dbx) list So, it looks like eptr is not null (which is why it isn't caught by the So why would va_arg return something that's invalid? I'm assuming that (dbx) where (dbx) print *args diff'ing sv.c between 5.12.4 and 5.14.2 turns up a lot of changes, so Suggestions for next steps to take? Tim |
From @hvdsTim Mooney <Tim.Mooney@ndsu.edu> wrote: That's in Perl_newSVpvf: :(dbx) where The stack trace shows a discrepancy: [3] received '(nil)' for args, HTH, Hugo |
From Tim.Mooney@ndsu.eduOn Wed Apr 18 01:25:10 2012, hv wrote:
I think that's just a display artifact because the optimizer may have I rebuilt 5.14.2 with -xinline= (i.e. all inlining turned off) and I 12:26 PM dogbert perl-5.14.2$t/perl -I lib t/op/getpid.t (dbx) up |
From @hvds"Tim.Mooney@ndsu.edu via RT" <perlbug-followup@perl.org> wrote: Ok, I guess the first question should have been: is the value being passed As far as I can see it should not be: the calling code from Note this is happening within sv_kill_backrefs, which has had several But for diagnosing this issue, I think the next step should be to try Hugo |
From Tim.Mooney@ndsu.eduIn regard to: Re: [perl #100450] perl 5.14.2 test suite failures on...:
(dbx) up
I dropped the optimization to -xO2 for just sv.o and the problem no I'll check 5.16 once it's actually released, to see if the issue is still Tim |
From @khwilliamsonOn Thu Apr 19 12:26:11 2012, enchanter wrote:
5.16 is now out. Please see if the issue got fixed. |
From @cpansproutFixed by 1bac5ec, according to #91678. |
From [Unknown Contact. See original ticket]Fixed by 1bac5ec, according to #91678. |
@cpansprout - Status changed from 'open' to 'resolved' |
From Tim.Mooney@ndsu.eduOn Wed Aug 22 08:35:04 2012, sprout wrote:
Sorry for the delay in responding. I can confirm that #91678 is Thanks! |
Migrated from rt.perl.org#100450 (status was 'resolved')
Searchable as RT100450$
The text was updated successfully, but these errors were encountered: