Re: [PHP4BETA] zend_handle_sigsegv and --enable-debug
| From: | Zeev Suraski | Date: | Mon, 05 Jul 1999 01:08:00 +0000 |
| Subject: | Re: [PHP4BETA] zend_handle_sigsegv and --enable-debug | ||
| References: | 1 2 3 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-1884@lists.php.net to get a copy of this message | ||
If I can't figure out why it fucks the trace so badly before Beta 1, we'll just comment out the signal() call that sets this handler up...
Zeev
At 13:08 04/07/99 , Sascha Schumann wrote:
It doesn't always do that, but it often does. I haven't played with it too much; If you can figure out why it does that, let me know. Anyway, it would make no sense to disable it when debug is on, since it's a debug tool. I meant to say to generally disable it, not to turn in on, when debug is off. ;-) But unless we can figure out, how to avoid this problem, it doesn't make much sense to turn it on. A backtrace of the form (gdb) bt #0 0x0 in ?? () #1 0x1200291b4 in zend_handle_sigsegv (dummy=11) at zend_execute_API.c:52 #2 0x1200291b4 in zend_handle_sigsegv (dummy=500) at zend_execute_API.c:52 doesn't help you a single bit. Else, people will have to disable it manually to generate useful backtraces. ---- Zeev Suraski <zeev@zend.com> http://www.zend.com/ For a PGP public key, finger bourbon@netvision.net.ilRegards,Sascha Schumann Consultant-- PHP 4 Beta