Package: libapache-mod-perl Version: 1.29.0.4-2 Severity: normal You're probably aware of this, but running unescape_url on a constant value yields a "Modification of a read-only value attempted" error message.
Although it may seem unlikely at first, this is the kind of stuff that happens when debugging; you run unescape_url('foo=bar') to make sure that this part works, and then you wonder why things suddenly got worse. Since I assume this is a desired optimization (and will therefore not be removed), could unescape_url check SvREADONLY(sv), and either spawn a copy of sv or croak/die in this case? (In the latter case, it'd be nice if at least Apache::Util's unescape_url wasn't subject to this restriction.) -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-toroia Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1) Versions of packages libapache-mod-perl depends on: ii apache-common 1.3.34-2 support files for all Apache webse ii libc6 2.3.6-15 GNU C Library: Shared libraries ii libdevel-symdump-perl 2.03-3 Perl module for inspecting perl's ii libperl5.8 5.8.8-6 Shared Perl library ii liburi-perl 1.35-2 Manipulates and accesses URI strin ii libwww-perl 5.805-1 WWW client/server library for Perl ii perl [libmime-base64-perl] 5.8.8-6 Larry Wall's Practical Extraction libapache-mod-perl recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]