, 15 Oct 2002 12:15:07 -0700 (PDT)
From: Aaron Gowatch <[EMAIL PROTECTED]>
To: Aaron Gowatch <[EMAIL PROTECTED]>
Cc: Andi Gutmans <[EMAIL PROTECTED]>,
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
Subject: Re: [PHP-DEV] Re: Segfaults in 4.2.3?
Heres some mor
Andi --
I'm still trying to track that down. Given the backtrace below, is it
possible to find out what script or function was executing when the
process SIGSEGV'd? I read the docs on bugs.php.net on diagnosing crashes
with gdb, but this looks a little different (ie. theres no execute() in
this
What we'd really need is a short 10-20 line reproducing script.
Andi
At 11:20 AM 10/14/2002 -0700, Aaron Gowatch wrote:
>Heres a backtrace from one of my SIGSEGVs. This one looks a little
>different from previous segfaults, but perhaps it can help track this bug
>down:
>
>Program received signa
Heres a backtrace from one of my SIGSEGVs. This one looks a little
different from previous segfaults, but perhaps it can help track this bug
down:
Program received signal SIGSEGV, Segmentation fault.
0x42082a0c in memcpy () from /lib/i686/libc.so.6
(gdb) bt
#0 0x42082a0c in memcpy () from /li
