Skip to content
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.

ExceptionHandler trace args size problem #16

Open
Ragazzo opened this issue Dec 10, 2015 · 2 comments
Open

ExceptionHandler trace args size problem #16

Ragazzo opened this issue Dec 10, 2015 · 2 comments

Comments

@Ragazzo
Copy link

Ragazzo commented Dec 10, 2015

Currently there is a problem with print_r in ExceptionHandler formatter, if argument is an object and not simple POCO / DTO but one that contains links to other objects and so on, it becomes very not trivial to dump exception message.

For example, with DoctrineModule, DoctrineORMModule configured in application if i make test exception throw in onBootstrap of module throw new Exception('Evil exception occured'); then the only argument of first trace will be MvcEvent but since it contains information about a lot of in application my memory limit is not enough to log exception, even 512 Mb not enough to log exception.

Possible solution:

would be greate to introduce to ExceptionHandler attribute like traceArgumentLevel that will dump object only to needed level as Doctrine2 Debug::dump does.

@Maks3w what your thoughs on this one?

@Ragazzo
Copy link
Author

Ragazzo commented Dec 17, 2015

bump

@weierophinney
Copy link
Member

This repository has been closed and moved to laminas/laminas-log; a new issue has been opened at laminas/laminas-log#8.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants