Closed p5pRT closed 21 years ago
Folks\,
looks like the Perl bug system was having some problems the other day. I am re-sending my bug report\, with a few additional notes:
1. Removing the Autoloader did *not* fix the problem.
2. We are now at a complete loss.
Any suggestions\, assistance\, additional debugging requests\, etc. would be greatly appreciated.
David.
** WARNING ** This message was composed by a temporarily crippled programmer using a speech recognition system. Please don't be alarmed if some extremely strange word usage shows up in the message. Many thanks....
---------- Forwarded message ---------- Date: Wed\, 9 Jun 1999 18:55:35 -0400 From: Mail Delivery Subsystem \MAILER\-DAEMON@​perl\.org To: davidb@chelsea.net Subject: Returned mail: unknown mailer error 13
The original message was received at Wed\, 9 Jun 1999 18:55:30 -0400 from IDENT:root@perl.com [199.45.135.9]
----- The following addresses had permanent fatal errors ----- "|/home/richard/bugs/scripts/tm_mailproc.pl" (expanded from: \perlbugtron@​perl\.org)
----- Transcript of session follows -----
RFgen::logg(Initial: [12849] (/home/richard/bugs/logs/pb_19990609) /home/richard/bugs/scripts/tm_mailproc.pl set) can't open today's log (/home/richard/bugs/logs/pb_19990609)! Permission denied at /home/richard/site_perl/RFgen.pm line 193\, \
Delivery Status: Reporting-MTA: dns; defender.perl.org Received-From-MTA: DNS; perl.com Arrival-Date: Wed, 9 Jun 1999 18:55:30 -0400
Final-Recipient: RFC822; perlbugtron@perl.org X-Actual-Recipient: RFC822; |/home/richard/bugs/scripts/tm_mailproc.pl@defender.perl.org Action: failed Status: 5.0.0 Last-Attempt-Date: Wed, 9 Jun 1999 18:55:35 -0400
Message RFC822: Return-Path: davidb@chelsea.net Received: from jhereg.perl.com (IDENT:root@perl.com [199.45.135.9]) by defender.perl.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id SAA12846 for perlbugtron@perl.org; Wed, 9 Jun 1999 18:55:30 -0400 Received: from killian.chelsea.net (killian.chelsea.net [207.25.36.14]) by jhereg.perl.com (8.9.0/8.9.0) with ESMTP id GAA09814 for perlbug@perl.com; Wed, 9 Jun 1999 06:41:27 -0600 Received: from spaten.chelsea.net (spaten.chelsea.net [207.25.36.16]) by killian.chelsea.net (8.9.1/8.9.1) with ESMTP id IAA03310; Wed, 9 Jun 1999 08:41:37 -0400 (EDT) From: David Birnbaum davidb@chelsea.net Received: (from davidb@localhost) by spaten.chelsea.net (8.9.1/8.9.1) id IAA17614; Wed, 9 Jun 1999 08:41:36 -0400 (EDT) Date: Wed, 9 Jun 1999 08:41:36 -0400 (EDT) Message-Id: 199906091241.IAA17614@spaten.chelsea.net To: perlbug@perl.com Cc: tech@chelsea.net Subject: Random core dump MIME-Version: 1.0
This is a bug report for perl from davidb@chelsea.net, generated with the help of perlbug 1.26 running under perl 5.00502.
[Please enter your report here]
We have suddenly become perplexed with a core dump that occurs approximately once every three or four times we run a particular Perl program. Unfortunately, the library being included is rather long, and I can't include a small sample program to reproduce the error. However, here is information I can provide:
We are using the Autoloader module. The problem seems to go away when we turn it off, but we want to run a few more nights to make certain.
We cannot reproduce the problem when perl is running under a "truss", even after dozens of attempts.
The problem showed up when we made this change to a signal handling routine in the library:
* 33,42 **
@ISA = qw( AutoLoader );
! $SIG{"CHLD"} = sub { $Admutil::last_pid = waitpid( -1, WNOHANG ); $Admutil::caught_pid{$Admutil::last_pid} = $?; };
#
--- 33,44 ----
@ISA = qw( AutoLoader );
! sub REAPER { ! $SIG{"CHLD"} = \&REAPER; $Admutil::last_pid = waitpid( -1, WNOHANG ); $Admutil::caught_pid{$Admutil::last_pid} = $?; };
$SIG{"CHLD"} = \&REAPER;
#
which was to try and debug a problem with "unknown subroutine" appearing another part of the code - occasionally (suspicious, me thinks).
(gdb) where
is what it has to say about where it is dying.
I'm sorry I cannot include anything more useful. Hopefully this will jog somebody's memory about a potential cause or can give us a few new ideas to try.
Thanks,
David.
Site configuration information for perl 5.00502:
Configured by mprewitt at Sat Dec 5 09:54:18 EST 1998.
Summary of my perl5 (5.0 patchlevel 5 subversion 2) configuration: Platform: osname=solaris, osvers=2.6, archname=sun4-solaris uname='sunos corona 5.6 generic_105181-09 sun4m sparc sunw,sparcstation-20 ' hint=previous, useposix=true, d_sigaction=define usethreads=undef useperlio=undef d_sfio=undef Compiler: cc='gcc', optimize='-O', gccversion=2.8.1 cppflags='-I/opt/bind/8.1.2/include -I/usr/local/include' ccflags ='-I/opt/bind/8.1.2/include -I/usr/local/include' stdchar='unsigned char', d_stdstdio=define, usevfork=false intsize=4, longsize=4, ptrsize=4, doublesize=8 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16 alignbytes=8, usemymalloc=y, prototype=define Linker and Libraries: ld='gcc', ldflags ='-L/opt/bind/8.1.2/bind/lib -L/usr/local/lib' libpth=/usr/local/lib /lib /usr/lib /usr/ccs/lib libs=-lsocket -lnsl -ldl -lm -lbind -lc -lcrypt libc=/lib/libc.so, so=so, useshrplib=false, libperl=libperl.a Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' ' cccdlflags='-fPIC', lddlflags='-G -L/usr/local/lib -L/opt/bind/8.1.2/bind/lib'
Locally applied patches:
@INC for perl 5.00502: /opt/perl/5.005_02/lib/perl/sun4-solaris /opt/perl/5.005_02/lib/perl /opt/siteperl/5.005_02/siteperl/sun4-solaris /opt/siteperl/5.005_02/siteperl .
Environment for perl 5.00502: HOME=/home/davidb LANG (unset) LD_LIBRARY_PATH (unset) LOGDIR (unset) PATH=/home/davidb/bin:/usr/local/bin:/usr/sbin:/usr/bin:/usr/ccs/bin:/usr/ucb:. PERL_BADLANG (unset) SHELL=/bin/ksh
Folks\,
We are proceeding under the assumption that this bug is actually a core dump from a malloc() call in a signal handler (as per various and sundry comments in the Perl book). Is there any way to verify this? In any case\, we are modifying our code to see if that is indeed the case. Wish we knew why it suddenly started....
Thanks (if anyone is indeed out there).
David.
** WARNING ** This message was composed by a temporarily crippled programmer using a speech recognition system. Please don't be alarmed if some extremely strange word usage shows up in the message. Many thanks....
---------- Forwarded message ---------- Date: Mon\, 14 Jun 1999 09:35:52 -0400 From: Richard Foley \richard@​perl\.org To: David Birnbaum \davidb@​chelsea\.net Subject: [ID 19990614.001 Perl core dump]
Your e-mail has been received by the Perl Bug Squashing Team.
Ticket ID '[19990614.001]' has been assigned. Please include this ticket ID in the subject line of any followup messages related to this issue.
This is an automatic confirmation message. -- Perl Bug Squashing Team perlbug@perl.org
That appears to be a screen shot of an Amazon Lambda information page.
Yves
On Fri, 25 Oct 2024 at 06:23, Diego Lesmes @.***> wrote:
Screenshot.2024-10-24.at.11.12.02.PM.png (view on web) https://github.com/user-attachments/assets/62d0d555-3236-4477-bbf8-dee07847c4a1
— Reply to this email directly, view it on GitHub https://github.com/Perl/perl5/issues/64#issuecomment-2436796055, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAZ5R57ZOQEH3JC7MOX6TDZ5HBUBAVCNFSM6AAAAABQSNSK32VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZWG44TMMBVGU . You are receiving this because you are subscribed to this thread.Message ID: @.***>
-- perl -Mre=debug -e "/just|another|perl|hacker/"
Migrated from rt.perl.org#865 (status was 'resolved')
Searchable as RT865$