Your message dated Tue, 15 Apr 2008 08:20:28 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#471409: lighttpd: SEGV when daemon spawns child; 
clone() call segfaults
has caused the Debian Bug report #471409,
regarding lighttpd: SEGV when daemon spawns child; clone() call segfaults
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.)


-- 
471409: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471409
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: lighttpd
Version: 1.4.19-1
Severity: normal

hi,

i'm filing this from an x86 box, but the bug is in PPC, i don't see this 
behaviour 
in x86. i've run the daemon through strace, and right when it spawns off a 
child with
clone(), the parent SEGVs, making the pid file for s-s-d, and other issues, go 
buggery.


a bit before, and a bit after what i said:

=====
12428 rt_sigaction(SIGTTOU, {SIG_IGN}, {SIG_DFL}, 8) = 0
12428 rt_sigaction(SIGTTIN, {SIG_IGN}, {SIG_DFL}, 8) = 0
12428 rt_sigaction(SIGTSTP, {SIG_IGN}, {SIG_DFL}, 8) = 0
12428 clone(child_stack=0, 
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x4801c3e8) 
= 12429
12428 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
12429 rt_sigaction(SIGPIPE, {SIG_IGN},  <unfinished ...>
12428 +++ killed by SIGSEGV +++
12429 <... rt_sigaction resumed> {SIG_DFL}, 8) = 0
12429 getsockname(11, {sa_family=AF_FILE, [EMAIL PROTECTED], [2]) = 0
12429 getpeername(11, {sa_family=AF_FILE, path="/var/run/slapd/ldapi"}, [23]) = 0
12429 fcntl64(11, F_GETFD)              = 0x1 (flags FD_CLOEXEC)
=====

the bug has existed since a few package versions ago. i've tried backports, 
same problem.
as a consequnce of this bug, the package configuration fails.

thanks
simon



-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: powerpc

Kernel: Linux 2.6.24.2-acahkos
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lighttpd depends on:
ii  libattr1               1:2.4.41-1        Extended attribute shared library
ii  libbz2-1.0             1.0.4-4           high-quality block-sorting file co
ii  libc6                  2.7-9             GNU C Library: Shared libraries
ii  libgamin0 [libfam0]    0.1.9-2           Client library for the gamin file 
ii  libldap-2.4-2          2.4.7-6.1         OpenLDAP libraries
ii  libpcre3               7.6-2             Perl 5 Compatible Regular Expressi
ii  libssl0.9.8            0.9.8g-7          SSL shared libraries
ii  libterm-readline-perl- 1.0302-1          Perl implementation of Readline li
ii  lsb-base               3.2-4             Linux Standard Base 3.2 init scrip
ii  mime-support           3.40-1.1          MIME files 'mime.types' & 'mailcap
ii  zlib1g                 1:1.2.3.3.dfsg-11 compression library - runtime

lighttpd recommends no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
On Mon, Apr 14, 2008 at 10:15:14PM +0000, Simon Raven wrote:
> On 13/04/2008, Pierre Habouzit <[EMAIL PROTECTED]> wrote:
> 
> >
> >   Then use gdb to read the backtrace.
> >
> >   Running lighttpd under valgrind may help.
> 
> valgrind doesn't exist for PPC IIRC;

  It does.
 
> just close this bug, thanks. i don't really care about this enough to
> do anything more about it. not my usual approach to these things, but
> I don't want to deal with more headaches.

  err well okay.

-- 
·O·  Pierre Habouzit
··O                                                [EMAIL PROTECTED]
OOO                                                http://www.madism.org

Attachment: pgpZEGeCgc4PV.pgp
Description: PGP signature


--- End Message ---

Reply via email to