Ticket #811 (closed enhancement: wontfix)

Opened 7 months ago

Last modified 2 months ago

Implement new application mode, Trace.

Reported by: sergeymorkovkin Owned by: xue
Priority: low Milestone:
Component: Prado Framework v3 Version: 3.1
Severity: minor Keywords:
Cc:

Description

I suggest to implement new application mode called 'Trace'.

We encode our application using IonCube? and sometimes we trap into situations when some php module doesn't return execution of a program or for some reason application terminates at some point. This depends on customer environment.

To figure out what line of code produced an exception we need to recompile the whole project with fil_put_contents traces several times and upload it on server several times until we know what exactly was the cause.

I suggest adding trace mode to write all application execution points into a separate file. This file must not be releated with logging module since tracing is also needed before and during modules initialization.

Change History

Changed 7 months ago by maddin

This is really a bit special and blows the source code up very much. I think the better solution is to implement such a Trace-Component and add the traces at some specific points. You may share it with the community, but i don't think that the prado-core should include all the traces (or may be a pradotraced.php, like the pradolite.php).

Changed 2 months ago by knut

  • status changed from new to closed
  • resolution set to wontfix

You should use Xdebug for tracing.

Note: See TracTickets for help on using tickets.