Package: php4-rrdtool
Version: 1.04-15
Severity: important

I have a horrible feeling this is just me, because I can't believe
no-one else is experiencing it...

Any use of the RRD extensions since 1.04-15 in PHP4 by my scripts causes the 
apache
sub-processes to immediately segfault, before anything is even logged to
the access.log. All I get is repetitions of:

[Mon Sep 26 18:31:49 2005] [notice] child pid 19613 exit signal Segmentation 
fault (11)
[Mon Sep 26 18:31:49 2005] [notice] child pid 19614 exit signal Segmentation 
fault (11)
[Mon Sep 26 18:31:49 2005] [notice] child pid 19620 exit signal Segmentation 
fault (11)

...in /var/log/apache/error.log, and "Zero Sized Reply" to my requests.

I'm sorry this isn't a very complete bug report, but since it's breaking
the package (for me at least), I thought I'd better report it anyway.
There's nothing in the changelog, FAQ or README to point out where I
might be awry.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (900, 'unstable'), (500, 'testing'), (200, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12.200506221
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) (ignored: LC_ALL set to 
en_GB)

Versions of packages php4-rrdtool depends on:
ii  debconf [debconf-2.0]         1.4.58     Debian configuration management sy
ii  libapache-mod-php4 [phpapi-20 4:4.4.0-2  server-side, HTML-embedded scripti
ii  libc6                         2.3.5-6    GNU C Library: Shared libraries an
ii  librrd2                       1.2.11-0.4 Time-series data storage and displ
ii  php4-cgi [phpapi-20050606]    4:4.4.0-2  server-side, HTML-embedded scripti
ii  php4-cli [phpapi-20050606]    4:4.4.0-2  command-line interpreter for the p

php4-rrdtool recommends no packages.

-- debconf information:
  php4/add_extension: true
* php4/extension_rrdtool_apache: true
  php4/remove_extension: true
* php4/extension_rrdtool_cgi: true
* php4/extension_rrdtool_cli: true


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to