Re: Stacktrace in errormessages
| From: | Gaylord Aulke | Date: | Sun, 29 Oct 2000 17:38:56 +0000 |
| Subject: | Re: Stacktrace in errormessages | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-36355@lists.php.net to get a copy of this message | ||
Hi,
please forgive me jumping in. i asked for this feature a few months
ago. in the moment the lack of a stack trace in error messages is
one limiting factor that prevents us from building bigger web-appz
with PHP. we currently have PHP appz running with hundreds of include
files all defining functions, classes and variables. with the error
messages PHP gives us, it is sometimes really hard to guess where the
error actually comes from.
how about an option in php.ini that enables building the needed data
structures as ragnar suggested?
regards,
gaylord aulke
AGI, stuttgart, germany
* fight complexity *
Zeev Suraski wrote:
>
> At 18:25 29-10-00, Ragnar Kjørstad wrote:
> >On Sun, Oct 29, 2000 at 06:23:06PM +0200, Zeev Suraski wrote:
> > > The function_call_stack is a compile-time data structure. It won't give
> > > you anything in runtime.
> >
> >And there is no stack for php-functions in runtime?
>
> No
>
> >If no, could you give me some hints to where this stack should be
> >modified?
> >
> >I'll try to add the feature - even if you don't think it belongs in the
> >php distribution it will be a nice feature for us and possible others.
> >(Or if you choose, you can add it with a compile-option).
>
> Well, it'd have to be added to the execute() code. As I said, though, we
> don't want to add it because it'll significantly reduce function call
> performance.
>
> Zeev
>
> --
> Zeev Suraski <zeev@zend.com>
> http://www.zend.com/
>
> --
> PHP Development Mailing List <http://www.php.net/>
> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net
> For additional commands, e-mail: php-dev-help@lists.php.net
> To contact the list administrators, e-mail: php-list-admin@lists.php.net