Re: Apache segfaults after Midgard 1.6.3 install
Sam Przyswa <samp-pAC44m+R7J2pwVsU+up1+gC/[email protected]>
| Newsgroups | gmane.comp.web.midgard.user |
|---|---|
| Message-ID | <[email protected]> |
X-MailScanner-Information Please contact the ISP for more information X-Arial Concept-MailScanner: Found to be clean Sam Przyswa a écrit : > X-MailScanner-Information Please contact the ISP for more information > X-Arial Concept-MailScanner: Found to be clean > > Piotras a écrit : > >> Try to reproduce segfault. >> >> Link to gdb simple howto. >> http://www.midgard-project.org/community/development/debugging.html >> >> > > After back to 2.4.27 kernel, load a gdb compiled Apache, gdb says: > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 16384 (LWP 1201)] > 0x40235ede in mallopt () from /lib/libc.so.6 After upgraded libc6, recompile Midgard I got: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 19589)] 0x40235fb1 in _int_malloc () from /lib/libc.so.6 With apache 1.3.33, PHP 4.3.4, Midgard 1.6.3, OpenSSL 0.9.7c, mod_perl 1.29 Sam. -- Ce message a été vérifié par MailScanner pour des virus ou des polluriels et rien de suspect n'a été trouvé.