Bug#449027: vserver: [notice] child pid 27907 exit signal Segmentation fault (11)

Hi Stefan, do you think, that this bug is related to this one: non-async-signal-safe operations from signal handlers httpd-2 http://issues.apache.org/bugzilla/show_bug.cgi?id=23238 I guess not, because it's in apache2. This might be interesting, too. It's more related to perl: Re: How to get a cor

Bug#449027: vserver: [notice] child pid 27907 exit signal Segmentation fault (11)

Am Mittwoch, 14. November 2007 schrieben Sie: > On Sunday 11 November 2007, Gerhard Gaußling wrote: > > #0  0xb7ff26e5 in do_lookup_x () from /lib/ld-linux.so.2 > > #1  0xb7ff2b07 in _dl_lookup_symbol_x () from /lib/ld-linux.so.2 > > #2  0xb7ff62f9 in fixup () from /lib

Bug#449027: vserver: [notice] child pid 27907 exit signal Segmentation fault (11)

Zur passenden Dateiberechtigung des coredump-Verzeichnisses: # ls -ld /coredump drwxrwxrwx 2 www-data www-data 1024 2007-11-11 23:12 /coredump http://httpd.apache.org/dev/debugging.html I did also a session with the command "where": # gdb /usr/sbin/apache.dbg -c /coredump/core.28525 [...]

Bug#449027: vserver: [notice] child pid 27907 exit signal Segmentation fault (11)

Hello Stefan, I''m sorry, because it was due to directory permissions, that I didn't get core dumps, oops... Finally I get now coredumps, but I'm not able to decipher them. I started apache this way: # /usr/sbin/apache.dbg -f /etc/apache/httpd.conf And used gallery2 webapp to get the sigseg 11

Bug#449027: vserver: [notice] child pid 27907 exit signal Segmentation fault (11)

Hello Stefan, I'm sorry, I give it up, because I can't see how to get the CoreDumps: [Sun Nov 11 22:12:26 2007] [notice] child pid 21908 exit signal Segmentation fault (11) # find /home/www/tmp/ -iname "*core*" # ls -ld /home/www/tmp drwxrws--- 2 root www-data 172032 2007-11-11 20:25 /home/www/

Bug#449027: vserver: [notice] child pid 27907 exit signal Segmentation fault (11)

Hello, I don't want to spam this bug report with logs, although I don't know what's going wrong. I'm not able to get a coredump again, and gdb crashes all the time. Therefore I come again with this huge report, I'm sorry: # uname -a Linux pv10.ncsrv.de 2.6.9-023stab044.11-smp #1 SMP Sat Sep 29

Bug#449027: vserver: [notice] child pid 27907 exit signal Segmentation fault (11)

Am Freitag, 9. November 2007 schrieben Sie: > On Saturday 03 November 2007, Gerhard Gaußling wrote: > > You're using a 32-bit installation with a 64-bit kernel, right? > > > > GDB doesn't work in this configuration.  It's a kernel bug; the > > pt

Bug#449027: vserver: [notice] child pid 27907 exit signal Segmentation fault (11)

I know now the reason of the dbg error: http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg340219.html Bug#421270 You're using a 32-bit installation with a 64-bit kernel, right? GDB doesn't work in this configuration. It's a kernel bug; the ptrace 32-bit emulation does not handle

Bug#449027: vserver: [notice] child pid 27907 exit signal Segmentation fault (11)

Hello Stefan, unfortunately the gdb problem is still there, and it stops the debug process. Therefore I tried it with ExceptionHooks and the core.dump module, to get something out of the apache: # gdb --args /usr/sbin/apache.dbg -F -X -f /etc/apache/httpd.conf GNU gdb 6.4.90-debian Copyright (C

Bug#449027: vserver: [notice] child pid 27907 exit signal Segmentation fault (11)

I checked once again the vserver resources: # bin/vpsmem - VPS Speichernutzung Hardware Node Memory [XXX=] Total: 7950 MB Momentan: 90% Barriere Frei: 920 MB Fehlversuche:42 Fehler

Bug#449027: vserver: [notice] child pid 27907 exit signal Segmentation fault (11)

I catched a new created apache pid 7963 by observe `watch -n 0 ps axuf`, and used it instantly by strace -p. That way I was able to catch an strace output of the segfault, it looks similar to the strace in the polish thread, I mentioned in the first post of this bugreport: # strace -p 7963 Proc

Bug#449027: vserver: [notice] child pid 27907 exit signal Segmentation fault (11)

Hallo Stefan, thank you for the response. I did an ` aptitude install apache-dbg libc6-dbg` and reenabled mod_backtrace and mod_whatkilledus, but I 'm afraid, the messages are all the same: # gdb --args apache -F -X -f /etc/apache/httpd.conf GNU gdb 6.4.90-debian Copyright (C) 2006 Free Software

Bug#449027: vserver: [notice] child pid 27907 exit signal Segmentation fault (11)

I think its not related to bug #411982 The error persists after a # dpkg -r php5-curl php5-pgsql and apachectl restart -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#449027: vserver: [notice] child pid 27907 exit signal Segmentation fault (11)

Sorry, I meant this bug, of course: php5 makes a segmentation fault when php5-curl and php5-pgsql installed http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411982 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#449027: vserver: [notice] child pid 27907 exit signal Segmentation fault (11)

This might be relatet to this bug, I'm not sure though: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=449027 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#449027: vserver: [notice] child pid 27907 exit signal Segmentation fault (11)

Package: apache Version: 1.3.34-4.1 Severity: normal This bug seems to be related to these bugs: #351654, #368315 I already started two threads about it, without a solution. I'm sorry, these threads are in german language, but with some interesting links and debug output: http://www.debianforum.d