[Bug 204033] New: *** glibc detected *** /usr/bin/perl: corrupted double-linked list: 0x08d1bec8 ***
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=204033
Summary: *** glibc detected *** /usr/bin/perl: corrupted double-
linked list: 0x08d1bec8 ***
Product: Fedora Core
Version: devel
Platform: i386
OS/Version: Linux
Status: NEW
Severity: normal
Priority: normal
Component: perl
AssignedTo: rnorwood(a)redhat.com
ReportedBy: caolanm(a)redhat.com
QAContact: dkl(a)redhat.com
CC: fedora-perl-devel-list(a)redhat.com
>From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.6) Gecko/20060822 Fedora/1.5.0.6-4 Firefox/1.5.0.6 pango-text
Description of problem:
crash during rpmbuild of openoffice.org
Version-Release number of selected component (if applicable):
perl-5.8.8-8
How reproducible:
Always
Steps to Reproduce:
1. 8 hours into rpmbuild -bb openoffice.org.spec
ok, not easy to reproduce :-)
Actual Results:
*** glibc detected *** /usr/bin/perl: corrupted double-linked list: 0x08d1bec8 ***
======= Backtrace: =========
/lib/libc.so.6[0xf7d3653a]
/lib/libc.so.6[0xf7d37f0e]
/lib/libc.so.6(cfree+0x90)[0xf7d38360]
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so(Perl_safesysfree+0x21)[0xf7f259e1]
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so(Perl_av_undef+0x83)[0xf7f33923]
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so(Perl_sv_clear+0x5b3)[0xf7f40153]
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so(Perl_sv_free+0x85)[0xf7f40485]
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so(Perl_sv_unref_flags+0x4f)[0xf7f4058f]
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so(Perl_sv_force_normal_flags+0x1be)[0xf7f40fbe]
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so(Perl_leave_scope+0xc55)[0xf7f64db5]
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so(Perl_pop_scope+0x35)[0xf7f64e95]
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so(Perl_pp_leave+0xe1)[0xf7f35a21]
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so(Perl_runops_standard+0x1f)[0xf7f347bf]
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so(perl_run+0x2ee)[0xf7eda21e]
/usr/bin/perl(main+0x13e)[0x80491ee]
/lib/libc.so.6(__libc_start_main+0xdc)[0xf7ce823c]
/usr/bin/perl[0x8049021]
======= Memory map: ========
08048000-0804b000 r-xp 00000000 09:01 6556913 /usr/bin/perl
0804b000-0804c000 rwxp 00002000 09:01 6556913 /usr/bin/perl
0804c000-0976a000 rwxp 0804c000 00:00 0
f7800000-f7821000 rwxp f7800000 00:00 0
f7821000-f7900000 ---p f7821000 00:00 0
f797f000-f798a000 r-xp 00000000 09:01 6357114 /lib/libgcc_s-4.1.1-20060818.so.1
f798a000-f798b000 rwxp 0000a000 09:01 6357114 /lib/libgcc_s-4.1.1-20060818.so.1
f798b000-f7b8c000 rwxp f7b8c000 00:00 0
f7c55000-f7c5e000 r-xp 00000000 09:01 6357173 /lib/libnss_files-2.4.90.so
f7c5e000-f7c5f000 r-xp 00008000 09:01 6357173 /lib/libnss_files-2.4.90.so
f7c5f000-f7c60000 rwxp 00009000 09:01 6357173 /lib/libnss_files-2.4.90.so
f7c5e000-f7c5f000 r-xp 00008000 09:01 6357173 /lib/libnss_files-2.4.90.so
f7c5f000-f7c60000 rwxp 00009000 09:01 6357173 /lib/libnss_files-2.4.90.so
f7c69000-f7c9e000 r-xs 00000000 09:00 229551 /var/db/nscd/passwd
f7c9e000-f7ca2000 r-xp 00000000 09:01 7325373 /usr/lib/perl5/5.8.8/i386-linux-thread-multi/auto/IO/IO.so
f7ca2000-f7ca3000 rwxp 00003000 09:01 7325373 /usr/lib/perl5/5.8.8/i386-linux-thread-multi/auto/IO/IO.so
f7ca3000-f7ca8000 r-xp 00000000 09:01 7325548 /usr/lib/perl5/5.8.8/i386-linux-thread-multi/auto/Socket/Socket.so
f7ca8000-f7ca9000 rwxp 00004000 09:01 7325548 /usr/lib/perl5/5.8.8/i386-linux-thread-multi/auto/Socket/Socket.so
f7ca9000-f7cab000 r-xp 00000000 09:01 7325315 /usr/lib/perl5/5.8.8/i386-linux-thread-multi/auto/Cwd/Cwd.so
f7cab000-f7cac000 rwxp 00001000 09:01 7325315 /usr/lib/perl5/5.8.8/i386-linux-thread-multi/auto/Cwd/Cwd.so
f7cac000-f7ccf000 rwxp f7cac000 00:00 0
f7ccf000-f7e06000 r-xp 00000000 09:01 6357157 /lib/libc-2.4.90.so
f7e06000-f7e08000 r-xp 00137000 09:01 6357157 /lib/libc-2.4.90.so
f7e08000-f7e09000 rwxp 00139000 09:01 6357157 /lib/libc-2.4.90.so
f7e09000-f7e0c000 rwxp f7e09000 00:00 0
f7e0c000-f7e1f000 r-xp 00000000 09:01 6357181 /lib/libpthread-2.4.90.so
f7e1f000-f7e20000 r-xp 00012000 09:01 6357181 /lib/libpthread-2.4.90.so
f7e20000-f7e21000 rwxp 00013000 09:01 6357181 /lib/libpthread-2.4.90.so
f7e21000-f7e23000 rwxp f7e21000 00:00 0
f7e23000-f7e25000 r-xp 00000000 09:01 6357189 /lib/libutil-2.4.90.so
f7e25000-f7e26000 r-xp 00001000 09:01 6357189 /lib/libutil-2.4.90.so
f7e26000-f7e27000 rwxp 00002000 09:01 6357189 /lib/libutil-2.4.90.so
f7e27000-f7e2c000 r-xp 00000000 09:01 6357161 /lib/libcrypt-2.4.90.so
f7e2c000-f7e2d000 r-xp 00004000 09:01 6357161 /lib/libcrypt-2.4.90.so
f7e2d000-f7e2e000 rwxp 00005000 09:01 6357161 /lib/libcrypt-2.4.90.so
f7e2e000-f7e55000 rwxp f7e2e000 00:00 0
f7e55000-f7e7a000 r-xp 00000000 09:01 6357165 /lib/libm-2.4.90.so
f7e7a000-f7e7b000 r-xp 00024000 09:01 6357165 /lib/libm-2.4.90.so
f7e7a000-f7e7b000 r-xp 00024000 09:01 6357165 /lib/libm-2.4.90.so
f7e7b000-f7e7c000 rwxp 00025000 09:01 6357165 /lib/libm-2.4.90.so
f7e7c000-f7e7e000 r-xp 00000000 09:01 6357163 /lib/libdl-2.4.90.so
f7e7e000-f7e7f000 r-xp 00001000 09:01 6357163 /lib/libdl-2.4.90.so
f7e7f000-f7e80000 rwxp 00002000 09:01 6357163 /lib/libdl-2.4.90.so
f7e80000-f7e81000 rwxp f7e80000 00:00 0
f7e81000-f7e93000 r-xp 00000000 09:01 6357167 /lib/libnsl-2.4.90.so
f7e93000-f7e94000 r-xp 00011000 09:01 6357167 /lib/libnsl-2.4.90.so
f7e94000-f7e95000 rwxp 00012000 09:01 6357167 /lib/libnsl-2.4.90.so
f7e95000-f7e97000 rwxp f7e95000 00:00 0
f7e97000-f7ea6000 r-xp 00000000 09:01 6357183 /lib/libresolv-2.4.90.so
f7ea6000-f7ea7000 r-xp 0000e000 09:01 6357183 /lib/libresolv-2.4.90.so
f7ea7000-f7ea8000 rwxp 0000f000 09:01 6357183 /lib/libresolv-2.4.90.so
f7ea8000-f7eaa000 rwxp f7ea8000 00:00 0
f7eb3000-f7fdd000 r-xp 00000000 09:01 7325177 /usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so
f7fdd000-f7fe2000 rwxp 00129000 09:01 7325177 /usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so
f7fe2000-f7fe5000 rwxp f7fe2000 00:00 0
f7fe5000-f7ffe000 r-xp 00000000 09:01 6357150 /lib/ld-2.4.90.so
f7ffe000-f7fff000 r-xp 00018000 09:01 6357150 /lib/ld-2.4.90.so
f7fff000-f8000000 rwxp 00019000 09:01 6357150 /lib/ld-2.4.90.so
fffe8000-ffffe000 rw-p fffe8000 00:00 0
ffffe000-fffff000 ---p 00000000 00:00 0
Abort
Expected Results:
Additional info:
There was a glibc bugfix recently which affected evolution, perhaps that's relevent
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
15 years, 10 months
[Bug 230406] New: MakeMaker has perl.mak depending on non-existent /usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/config.h'
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=230406
Summary: MakeMaker has perl.mak depending on non-existent
/usr/lib/perl5/5.8.8/i386-linux-thread-
multi/CORE/config.h'
Product: Fedora Core
Version: devel
Platform: i386
OS/Version: Linux
Status: NEW
Severity: medium
Priority: normal
Component: perl
AssignedTo: rnorwood(a)redhat.com
ReportedBy: vonbrand(a)inf.utfsm.cl
QAContact: dkl(a)redhat.com
CC: fedora-perl-devel-list(a)redhat.com
Description of problem:
I tried to build git here, the build fails:
make[2]: Entering directory `/home/vonbrand/tmp/git/perl'
make[2]: *** No rule to make target
`/usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/config.h', needed by
`perl.mak'. Stop.
The generated perl.mak file (essentially a Makefile with funny name) contains
the following:
PERL_INC = /usr/lib/perl5/5.8.8/sparc-linux-thread-multi/CORE
...
CONFIGDEP = $(PERL_ARCHLIB)$(DFSEP)Config.pm $(PERL_INC)$(DFSEP)config.h
...
$(FIRST_MAKEFILE) : Makefile.PL $(CONFIGDEP)
I don't see how this could ever have worked, as the $(CONFIGDEP) file doesn't
exist. Strangely, the same git does build OK on Aurora Linux (essentially an
oldish Fedora Core), with the exact same Makefile, where the referenced file
doesn't exist either.
I'm blaming perl as it is the only piece I think might be involved that changed
today, and before updating today the build went fine.
Version-Release number of selected component (if applicable):
perl-5.8.8-13.fc7
How reproducible:
Don't know.
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
15 years, 10 months
[Bug 207838] New: Perl getsockopt() on SCTP sockets doesn't work
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207838
Summary: Perl getsockopt() on SCTP sockets doesn't work
Product: Fedora Core
Version: fc5
Platform: x86_64
OS/Version: Linux
Status: NEW
Severity: normal
Priority: normal
Component: perl
AssignedTo: rnorwood(a)redhat.com
ReportedBy: pablo_p(a)op.pl
QAContact: dkl(a)redhat.com
CC: fedora-perl-devel-list(a)redhat.com
Description of problem:
Perl getsockopt() on SCTP socket does not work. Following perl code:
------------------------------------------
use strict;
use IO::Socket;
## create sctp socket
my $sock = new IO::Socket::INET(
Proto => 132,
Type => SOCK_STREAM
) or die "Cannot create sctp socket";
## read rto data
my $i = getsockopt($sock, 132, 1);
#print rto data
print join("\n", unpack("I i*", $i));
------------------------------------------
Works on Solaris10, but not on (my) Linux. I checked C getsockopt, and code like
this:
ret = getsockopt(sock , SOL_SCTP, SCTP_RTOINFO, &sctp_info, &len);
works OK only if len is initially set to sizeof(struct sctp_rtoinfo), which is
not what manual says:
-------------------------------------------
> man getsockopt
...
The parameters optval and optlen are used to access option values for
setsockopt(). For getsockopt() they identify a buffer in which the
value for the requested option(s) are to be returned. For getsock-
opt(), optlen is a value-result parameter, initially containing the
size of the buffer pointed to by optval, and modified on return to
indicate the actual size of the value returned. If no option value is
to be supplied or returned, optval may be NULL.
...
-------------------------------------------
Above applies to all SCTP structures available via get/setsockopt.
Version-Release number of selected component (if applicable):
perl-5.8.8-5
glibc-2.4-11
kernel-2.6.17-1.2187_FC5
How reproducible:
every time
Steps to Reproduce:
1. run perl code from description
2. nothing is displayed
Actual results:
nothing is displayed
Expected results:
sctp socket rto into (4 parameters)
Additional info:
SELinux is disabled.
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
16 years
[Bug 212369] New: Use of uninitialized value in pattern match
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=212369
Summary: Use of uninitialized value in pattern match
Product: Fedora Core
Version: fc6
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: normal
Component: spamassassin
AssignedTo: wtogami(a)redhat.com
ReportedBy: tjb(a)unh.edu
CC: fedora-perl-devel-
list@redhat.com,felicity@kluge.net,jm(a)jmason.org,parkerm
@pobox.com,reg+redhat@sidney.com,wtogami(a)redhat.com
Description of problem:
I'm running spamass-milter along with spamassassin and I'm seeing these errors
in /var/log/maillog:
Oct 26 09:19:19 raptor spamd[2509]: Use of uninitialized value in pattern match
(m//) at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line
879, <GEN4> line 5.
Oct 26 09:19:19 raptor spamd[2509]: Use of uninitialized value in concatenation
(.) or string at
/usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 953,
<GEN4> line 5.
The may be just warnings as mail is being tagged.
Also saw this:
Oct 26 11:28:21 raptor spamd[5990]: rules: meta test DIGEST_MULTIPLE has
undefined dependency 'DCC_CHECK'
Oct 26 11:28:21 raptor spamd[5990]: spamd: server started on port 783/tcp
(running version 3.1.4)
Version-Release number of selected component (if applicable):
spamassassin-3.1.4-1.fc6
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
16 years
[Bug 223753] New: Typo in /etc/logrotate.d/sa-update
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=223753
Summary: Typo in /etc/logrotate.d/sa-update
Product: Fedora Core
Version: fc6
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: normal
Component: spamassassin
AssignedTo: wtogami(a)redhat.com
ReportedBy: adrian(a)lisas.de
CC: fedora-perl-devel-
list@redhat.com,felicity@kluge.net,jm(a)jmason.org,parkerm
@pobox.com,reg+redhat@sidney.com,wtogami(a)redhat.com
Description of problem:
logrotate error message:
error: sa-update:3 unknown option 'notifyempty' -- ignoring line
Version-Release number of selected component (if applicable):
spamassassin-3.1.7-4.fc6
Fix:
Something like this:
/var/log/sa-update.log {
monthly
- notifyempty
+ notifempty
missingok
}
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
16 years
[Bug 235835] New: can you build for EL5?
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=235835
Summary: can you build for EL5?
Product: Fedora Extras
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: medium
Component: perl-IO-Multiplex
AssignedTo: lmb(a)biosci.ki.se
ReportedBy: bpeck(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: fedora-perl-devel-list(a)redhat.com
Description of problem:
I have a package in Extras called conmux which uses perl-IO-Multiplex on the
server side. I was wondering if you could build perl-IO-Multiplex for EL5 as well.
Thanks!
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
16 years, 1 month
Test::Pod::Coverage tests...
by Chris Weyl
Hey all--
So there's a rather spirited discussion perl packaging discussion
going on over at
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=237883 about
Test::Pod::Coverage module tests, and their importance.
The canonical approach is to insist on all tests being enabled that
possibly can -- even to the point of requiring other modules be
packaged to enable these tests. "Test as much as possible."
Test::Pod::Coverage tests don't actually test the functionality of the
module. Further, they can't tell you if that documentation is any
good, or even plain wrong. We also have a practice of disabling this
test out of hand if it fails for whatever reason... Further, usually
upstream takes the step of explicitly requiring this test be enabled
-- e.g. via TEST_POD=1 or some other mechanism.
Documentation coverage is a good Kwalitee indication (as they say),
not always an indication of good quality -- and certainly not a
consistent, reliable indication of that.
My opinion is that we ought to not mandate the use of Pod coverage
tests, simply because for our purposes it doesn't really matter what
their result is. If they're present, we should conditionalize the
tests (e.g. %_with_pod_tests magic or some such), but not insist on
them by default.
Either way, we ought to document this in Packaging/Perl -- which I
took a quick (and probably dirty) pass at reworking under
PackagingDrafts/Perl.
-Chris
--
Chris Weyl
Ex astris, scientia
16 years, 1 month
Bugzilla 3.0 Perl Requirements
by Max Kanat-Alexander
Hey folks. Just wanted to let you know that Bugzilla 3.0 (which
should be out soon) has a few perl pre-reqs that aren't in Extras. One
of them is required:
Email-Send
And all of the others are optional but still useful:
Template-GD
Email-MIME-Attachment-Stripper
Email-Reply
In particular, Template-GD really should be in FE--it was
originally part of Template-Toolkit and was moved out in version 2.15.
I figured I'd let you know sooner rather than later, when users
kept asking you for the packages, or when you had to build them anyway
to build a new Bugzilla package. :-)
-Max
--
http://www.everythingsolved.com/
Competent, Friendly Bugzilla Services. And Everything Else, too.
16 years, 1 month
[Bug 237612] New: WWW::Bugzilla fails to fetch bug
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=237612
Summary: WWW::Bugzilla fails to fetch bug
Product: Fedora Extras
Version: fc6
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: medium
Component: perl-WWW-Bugzilla
AssignedTo: jpo(a)di.uminho.pt
ReportedBy: cweyl(a)alumni.drew.edu
QAContact: extras-qa(a)fedoraproject.org
CC: fedora-perl-devel-list(a)redhat.com
Description of problem:
WWW::Bugzilla fails to fetch bug with:
Can't locate object method "form" via package "WWW::Mechanize" at
/usr/lib/perl5/vendor_perl/5.8.8/WWW/Bugzilla.pm line 271.
Version-Release number of selected component (if applicable):
perl-WWW-Mechanize-1.22-2.fc6
perl-WWW-Bugzilla-0.8-1.fc6
How reproducible:
Attempt to open an existing bug.
Actual results:
*boom* (see above)
Expected results:
A valid WWW::Bugzilla object to manipulate the given bug.
Additional info:
It appears WWW::Bugzilla 0.9 fixes this. Should be an easyfix as 0.9 is already
available in devel.
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
16 years, 1 month
[Bug 237594] New: Upgrade to SVK 2.0.1
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=237594
Summary: Upgrade to SVK 2.0.1
Product: Fedora Extras
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: medium
Component: perl-SVK
AssignedTo: ianburrell(a)gmail.com
ReportedBy: ianburrell(a)gmail.com
QAContact: extras-qa(a)fedoraproject.org
CC: fedora-perl-devel-list(a)redhat.com
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
16 years, 1 month