When fatal error occurs is it possible to output also the backtrace in the
error log? The simple error message with file line
only is quite useless...
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
When fatal error occurs is it possible to output also the backtrace in the
error log? The simple error message with file line
only is quite useless...
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
I think you need a PHP extension to do this. XDebug works rather nicely for
this.
On 31/08/2010, at 8:49 PM, Paul Freeman wrote:
> When fatal error occurs is it possible to output also the backtrace in the
> error log? The simple error message with file line
> only is quite useless...
>
> --
On 31 August 2010 09:49, Paul Freeman wrote:
> When fatal error occurs is it possible to output also the backtrace in the
> error log? The simple error message with file line
> only is quite useless...
outputs ...
In baz\bar
An error occurred.
array (
0 =>
array (
'file' => 'Z:\\bad.ph
Thanks!
I didn't notice the register_shutdown_function function.
But it executes always I want to run it only to track fatal error. Also I
can't get the backtrace properly:( I can't use 5.3 so I guess it works
differently in 5.2
Richard Quadling wrote:
> On 31 August 2010 09:49, Paul Freeman w
On 1 September 2010 13:38, wrote:
> Thanks!
> I didn't notice the register_shutdown_function function.
> But it executes always I want to run it only to track fatal error. Also I
> can't get the backtrace properly:( I can't use 5.3 so I guess it works
> differently in 5.2
>
> Richard Quadling wro
I'm curious if the behavior of json_encode() is influenced by the
browser at all. I have a page that returns search results. If I
access the page and perform a search using Chrome, the following error
shows up in the log:
PHP Warning: json_encode() [function.json-encode]: Invalid UTF-8
sequence
It can have something to do with your browser codification (UTF8,
ISO-8859-???).
--
João Cândido de Souza Neto
"Christoph Boget" escreveu na mensagem
news:aanlkti=45-heto2myhq116gv6bfxvdba_yxfzjnqk...@mail.gmail.com...
> I'm curious if the behavior of json_encode() is influenced by the
> br
You should set the charset of your page by meta tag in its head.
2010/9/1 Christoph Boget
> > It can have something to do with your browser codification (UTF8,
> > ISO-8859-???).
>
> But why would that be the case? Is json_encode() actually encoding
> the string differently in each case? And
> It can have something to do with your browser codification (UTF8,
> ISO-8859-???).
But why would that be the case? Is json_encode() actually encoding
the string differently in each case? And would it encode it
differently if I wrote a script to take the same input and ran it from
the command l
> You should set the charset of your page by meta tag in its head.
Do you have a source of reference to which you point me?
thnx,
Christoph
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
http://www.w3.org/TR/html4/charset.html
I hope it can help you.
PS: json_decode works only in utf8.
--
João Cândido de Souza Neto
"Christoph Boget" escreveu na mensagem
news:aanlktikpqdckrq7ctjwccgspz-c4fxpcnxxn_u48+...@mail.gmail.com...
>> You should set the charset of your page by meta t
> http://www.w3.org/TR/html4/charset.html
> I hope it can help you.
> PS: json_decode works only in utf8.
I understand charsets. I understand the difference between the
charsets. What I don't understand is how json_encode() is taking the
*exact same input* and behaving differently (breaking in o
Are you setting the charset in your html head?
If not, its using the charset set in your browser, which can be different
from one to another.
In this case, you must set if via meta tag to avoid it.
--
João Cândido de Souza Neto
"Christoph Boget" escreveu na mensagem
news:aanlktimbfbgunifh
Sorry about the error:
In this case, you must set IT via meta tag to avoid it.
--
João Cândido de Souza Neto
""João Cândido de Souza Neto"" escreveu na
mensagem news:16.27.07419.e0e5e...@pb1.pair.com...
> Are you setting the charset in your html head?
>
> If not, its using the charset set
> Sorry about the error:
> In this case, you must set IT via meta tag to avoid it.
Ok, let's try this using a different approach. Consider the following
pseudo-code:
Why does the charset of the browser matter one whit to the value of
either $row['name'] or $row['date'] such that it would break
In this case, you are right. It has nothing to do with the browser.
You´ll need a more detailed debug so you can see excatly what´s happening.
--
João Cândido de Souza Neto
"Christoph Boget" escreveu na mensagem
news:aanlktikctht0nxz1hi0ezj=i2m3716wepd=deppke...@mail.gmail.com...
>> Sorry
Hi
Can someone explain to me why I'm getting the 'dl() is deprecated' error?
I'm running PHP5.2.3 and I believe that I have the php.ini settings correct:
error.log:[2010-08-24T13:38:53] PC Error: dl()
[function.dl]: dl() is deprecated - use extension=test.so in your
php.ini
bash-2.05b$ php
I think the files included just when you call it to include. How do you mean
it later?
What's in that file? A class or direct code?
David Mehler wrote:
> Hello,
> I've got probably a simple question on require_once. I've got a file
> that has require_once at the top of it pulling in another file
I don't know that too.
I think the solution is to use your own error handler and save error in some
another file.
hovnocuc wrote:
> Hello,
>
> [ Question ]
> How do I force error_log to log only errors specified in the
> error_reporting directive? Is it even possible or did I get something
> wr
On Aug 31, 2010, at 3:06 PM, Ashley Sheridan wrote:
On Tue, 2010-08-31 at 15:01 -0500, Karl DeSaulniers wrote:
On Aug 31, 2010, at 2:32 PM, Ashley Sheridan wrote:
> On Tue, 2010-08-31 at 14:31 -0500, Karl DeSaulniers wrote:
>>
>> Hi,
>> Say I have some text.
>>
>> $text = 'You can logon here
21 matches
Mail list logo
