Your message dated Sun, 25 Dec 2011 21:55:48 +0100
with message-id <[email protected]>
and subject line Re: Bug#653223: [libforks-perl] Modification of a read-only
value attempted at forks/shared.pm:736
has caused the Debian Bug report #653223,
regarding [libforks-perl] Modification of a read-only value attempted at
forks/shared.pm:736
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
653223: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653223
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libforks-perl
Version: 0.34-1+b2
Severity: normal
--- Please enter the report below this line. ---
I tried forks as drop-in replacement for threads in the script I'm
writing and I'm getting this error message:
Modification of a read-only value attempted at
/usr/lib/perl5/forks/shared.pm line 736.
With threads it's working fine.
How can I help figuring out which code of mine actually causes that
error in fork's shared.pm?
Thanks!
Mit freundlichen Grüßen / Best regards
Marc H. Thoben
--- System information. ---
Architecture: amd64
Kernel: Linux 3.1.0-1-amd64
Debian Release: wheezy/sid
500 unstable www.debian-multimedia.org
500 unstable ftp.de.debian.org
500 stable dl.google.com
500 stable deb.opera.com
200 experimental ftp.de.debian.org
--- Package information. ---
Depends (Version) | Installed
========================================-+-==============
perl (>= 5.14.2-3) | 5.14.2-6
perlapi-5.14.2 |
libc6 (>= 2.2.5) | 2.13-23
libacme-damn-perl | 0.04-1+b2
liblist-moreutils-perl (>= 0.15) | 0.33-1+b1
libsys-sigaction-perl (>= 0.11) | 0.13-1
Package's Recommends field is empty.
Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---
On Sun, 25 Dec 2011 20:12:05 +0100, Marc H. Thoben wrote:
> >> How can I help figuring out which code of mine actually causes that
> >> error in fork's shared.pm?
> > You could run your script under the Perl debugger.
> That's exactly my problem, that I had (and still have) no idea how to
> debug Perl scripts.
The "classical" way is 'perl -d somescript.pl' but I admit it's not
always exactly helpful and convenient.
> Anyways, I assume this is a incompatibility between forks & Wx. Probably
> not worth keeping this bug report open.
Hm, yes, sounds at least like a rather complicated case.
> Please close it. Thanks!
Ok, closing it with this mail.
Cheers,
gregor
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key ID: 0x8649AA06
: :' : Debian GNU/Linux user, admin, & developer - http://www.debian.org/
`. `' Member of VIBE!AT & SPI, fellow of Free Software Foundation Europe
`- BOFH excuse #448: vi needs to be upgraded to vii
signature.asc
Description: Digital signature
--- End Message ---
