On 04.12.2007 17:07, Rachmel, Nir (Nir) wrote:
> Hi,
>
> Are there any tools you can recommend me for debugging my error?
> Standard gdb debugging doesn't seem to help, and using valgrind in a
> real-time webserver environment simply doesn't work on my device (or on
> anyone's device I guess.. :)
--
From: Antony Dovgal [mailto:[EMAIL PROTECTED]
Sent: Monday, December 03, 2007 5:41 PM
To: Rachmel, Nir (Nir)
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] FW: [PHP] PHP 5.2.3 segfault with syslog standard
extension
On 03.12.2007 18:19, Rachmel, Nir (Nir) wrote:
> Hi,
>
> I h
On 03.12.2007 18:19, Rachmel, Nir (Nir) wrote:
> Hi,
>
> I have been doing some code-reading. Why is the RSHUTDOWN function for
> syslog ext called only when run under win32?
> Shouldn't the cleanup happen on linux as well?
`man closelog` says it's not required.
DESCRIPTION
closelog() clo
11:31 AM
To: Antony Dovgal
Cc: internals@lists.php.net
Subject: RE: [PHP-DEV] FW: [PHP] PHP 5.2.3 segfault with syslog standard
extension
Hi,
I tried your advice, and put a breakpoint at the shutdown function.
However it never reaches it! (not normally, and not before the SEGV is
sent).
In case I d
ROTECTED]
Sent: Tuesday, November 27, 2007 8:40 AM
To: Rachmel, Nir (Nir)
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] FW: [PHP] PHP 5.2.3 segfault with syslog standard
extension
On 25.11.2007 19:55, Rachmel, Nir (Nir) wrote:
> If it helps, I am attaching the relevant tsrm_ls (according to th
On 25.11.2007 19:55, Rachmel, Nir (Nir) wrote:
> If it helps, I am attaching the relevant tsrm_ls (according to the
> globals_id in the relevant frame):
> syslog_started = 1,
> syslog_device = 0x5a5a5a5a ,
So it's somehow got freed.
Try setting breakpoint to zm_shutdown_syslog() function to
}
},
umask = -1
}
-Original Message-----
From: Antony Dovgal [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 25, 2007 4:37 PM
To: Rachmel, Nir (Nir)
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] FW: [PHP] PHP 5.2.3 segfault with syslog standard
extension
On 25.11.2007 17:30, Rach
ernals@lists.php.net
Subject: Re: [PHP-DEV] FW: [PHP] PHP 5.2.3 segfault with syslog standard
extension
On 25.11.2007 16:26, Rachmel, Nir (Nir) wrote:
> Here is a backtrace I extracted from the core:
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 8598
On 25.11.2007 17:30, Rachmel, Nir (Nir) wrote:
> Do you mean printing the 'tsrm_ls'?
> There is no 'basic_globals' symbol in the context of any of the frames I
> tried.
Oh, so this is multithreaded version..
That makes it even more complicated.
--
Wbr,
Antony Dovgal
--
PHP Internals - PHP Run
On 25.11.2007 16:26, Rachmel, Nir (Nir) wrote:
> Here is a backtrace I extracted from the core:
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 859800816 (LWP 15194)]
> 0x0fcdfa60 in free () from /lib/libc.so.6
> (gdb) bt
> #0 0x0fcdfa60 in free () from /lib/libc.s
Hi,
I am running PHP 5.2.3 as a statically compiled module for a web server
(appWeb, which is an embbeded apache-like server).
My platform is a ppc processor, running Windriver Linux.
The problem I encounter is, that when printing many syslogs to the
system my web-server crashes.
I have back
11 matches
Mail list logo
