I was originally opposed to adding this because I knew it could cause
problems. I haven't followed the arguments patch too closely except for
trying to fix crashes as well as I can.
I can try and look into it.
Andi
At 07:32 PM 4/8/2004 +0200, Magnus Määttä wrote:
On Thursday 08 April 2004 19.14
On Thursday 08 April 2004 19.14, Andi Gutmans wrote:
> Was this broken by my latest fix/patch or did it break before that? (I
> commited something yesterday).
It was broken before.
To be honest.. I have no idea when it worked as it should last time. I noticed
it a few days ago (3 or 4 maybe).
>
Andi Gutmans wrote:
Was this broken by my latest fix/patch or did it break before that? (I
commited something yesterday).
This is broken at least since beta 2 or 3, I don't remember when I first
noticed.
Patrick
--
use the source, luke
--
PHP Internals - PHP Runtime Development Mailing List
To
Was this broken by my latest fix/patch or did it break before that? (I
commited something yesterday).
At 11:43 AM 4/8/2004 -0400, Adam Maccabee Trachtenberg wrote:
On Thu, 8 Apr 2004, Magnus [iso-8859-15] Määttä wrote:
> debug_backtrace() used to print out arguments to functions, but does not
>
On Thu, 8 Apr 2004, Magnus [iso-8859-15] Määttä wrote:
> debug_backtrace() used to print out arguments to functions, but does not
> anymore. Is this desired behavior ?
I discovered this least night and it is already filed as a bug:
http://bugs.php.net/bug.php?id=27397
I'm hoping it's a bug, not
Hello
debug_backtrace() used to print out arguments to functions, but does not
anymore. Is this desired behavior ?
Output:
array(1) {
[0]=>
array(3) {
["file"]=>
string(36) "/home/magnus/Projects/base/test4.php"
["line"]=>
int(8)
["function"]=>
string(3) "foo"
}
