#19278 [Asn->Fbk]: SIGABRT during Apache startup with latest pspell

ID: 19278 Updated by: vlad@php.net Reported By: ast@domdv.de -Status: Assigned +Status: Feedback Bug Type: Pspell related Operating System: Linux 2.4 PHP Version: 4.2.3 Assigned To: vlad New Comment: I can not reproduce this. I am using the same version of aspell as you do, the same version of PHP, same version of apache and even same gcc. BTW: What makes you think that it's aspell that's crashing? Or did I miss something in your stack trace? Also, could you also compile it statically and see if that helps? Previous Comments: ------------------------------------------------------------------------ [2002-09-11 21:18:46] vlad@php.net I just checked latest aspell with php4.2.3 in CGI mode, and it seems to work well. I don't have an apache installation handy that I can hose, so further testing will have to wait a couple of days, but my guess is that I won't be able to reproduce your problem easily. ------------------------------------------------------------------------ [2002-09-10 20:09:52] vlad@php.net a lot (including some API) has changed since aspell and pspell got merged into one project. I don't know yet if that's why things don't work for you, but I'll look into it in a few days (as the time allows). Assigning to myself, unless someone else wants to pick it up. ------------------------------------------------------------------------ [2002-09-09 16:34:16] ast@domdv.de Hmm, I didn't check the library but at least the command line tool included in the package is verified to work properly. As I'm not familiar with the pspell library interface, could it be that the new library expects some parameter different than the old library (could still be a bug in new pspell)? ------------------------------------------------------------------------ [2002-09-09 14:48:03] kalowsky@php.net From my understanding of this, it looks like this is in the pspell library, and not PHP. Or is that not what you were trying to convay? ------------------------------------------------------------------------ [2002-09-07 09:44:07] ast@domdv.de In case of SIGABRT a stacktrace doesn't really help - but on request here it is. titanic:~ # gdb /usr/local/apache/bin/httpsd GNU gdb 5.2.1 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"... (no debugging symbols found)... (gdb) run -X Starting program: /usr/local/apache/bin/httpsd -X Reading key for server titanic.lan.domdv.de:443 Launching... /usr/local/apache/bin/gcache pid=3817 (no debugging symbols found)...(no debugging symbols found)... Program received signal SIGABRT, Aborted. 0x40254e61 in __kill () at __kill:-1 -1 __kill: No such file or directory. in __kill (gdb) bt #0 0x40254e61 in __kill () at __kill:-1 #1 0x40254c76 in raise () from /lib/libc.so.6 (gdb) quit The program is running. Exit anyway? (y or n) y titanic:~ # What may help more here is some other output: titanic:~ # ltrace /usr/local/apache/bin/httpsd -X <snip> malloc(24) = 0x080cd2c8 malloc(11) = 0x080cd2e8 malloc(21) = 0x080cd2f8 malloc(24) = 0x080cd318 malloc(5) = 0x080cd338 malloc(21) = 0x080cd348 malloc(24) = 0x080cd368 malloc(9) = 0x080cd388 malloc(21) = 0x080cd398 malloc(24) = 0x080cd3b8 malloc(9) = 0x080cd3d8 malloc(25) = 0x080cd3e8 __xstat(3, "/etc/cram-md5.pwd", 0xbffff46c) = -1 memset(0x0812e984, '\000', 28) = 0x0812e984 memset(0x0812e9a4, '\000', 16) = 0x0812e9a4 memset(0x0812e9f4, '\000', 20) = 0x0812e9f4 dup(2, 0x4055e660, 0x08094d84, 0x4042f23e, 0x0808b540) = 0 close(2) = 0 dup(1, 0x4055e660, 0x08094d84, 0x4042f23e, 0x0808b540) = -1 __assert_fail(0x0807e807, 0x0807df84, 1656, 0x0807e7e8, 0x0808b540 <unfinished . ..> --- SIGABRT (Aborted) --- +++ killed by SIGABRT +++ The above shows that an assertion in the pspell module fails. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/19278 -- Edit this bug report at http://bugs.php.net/?id=19278&edit=1