DDC-267: CLI does only show last error message and ignores stacked exceptions #333

Closed
opened 2026-01-22 12:35:04 +01:00 by admin · 7 comments
Owner

Originally created by @doctrinebot on GitHub (Jan 22, 2010).

Originally assigned to: @guilhermeblanco on GitHub.

Jira issue originally created by user shurakai:

If exceptions are stacked, only the last message is shown. The attached patch fixes this.

Originally created by @doctrinebot on GitHub (Jan 22, 2010). Originally assigned to: @guilhermeblanco on GitHub. Jira issue originally created by user shurakai: If exceptions are stacked, only the last message is shown. The attached patch fixes this.
admin added the Bug label 2026-01-22 12:35:04 +01:00
admin closed this issue 2026-01-22 12:35:06 +01:00
Author
Owner

@doctrinebot commented on GitHub (Jan 22, 2010):

Comment created by romanb:

Apparently there is a --trace option that, if enabled, shows the full stack trace.

Is that not sufficient? The patch merely concatenates exception messages, even without a separator.

The stack trace should probably always be shown?

@doctrinebot commented on GitHub (Jan 22, 2010): Comment created by romanb: Apparently there is a --trace option that, if enabled, shows the full stack trace. Is that not sufficient? The patch merely concatenates exception messages, even without a separator. The stack trace should probably always be shown?
Author
Owner

@doctrinebot commented on GitHub (Jan 22, 2010):

Comment created by shurakai:

Yes, I would disable --trace

The stacktrace is not sufficient because e.g. the ReflectionException generates a very useful message and is afterwards stacked by the MappingException to add more information, but the original message is lost...

Btw., yeah, maybe the output could be better ;)

@doctrinebot commented on GitHub (Jan 22, 2010): Comment created by shurakai: Yes, I would disable --trace The stacktrace is not sufficient because e.g. the ReflectionException generates a very useful message and is afterwards stacked by the MappingException to add more information, but the original message is lost... Btw., yeah, maybe the output could be better ;)
Author
Owner

@doctrinebot commented on GitHub (Jan 25, 2010):

Comment created by @guilhermeblanco:

The MappingException should be fixed then.
There's no reason to add a $e->getPrevious() lookup in CLIController.

Also... it's even a break in Exception class. There's no method prototype in PHP Exception class.

If MappingException is hiding something, point it to me and I fix it.

@doctrinebot commented on GitHub (Jan 25, 2010): Comment created by @guilhermeblanco: The MappingException should be fixed then. There's no reason to add a $e->getPrevious() lookup in CLIController. Also... it's even a break in Exception class. There's no method prototype in PHP Exception class. If MappingException is hiding something, point it to me and I fix it.
Author
Owner

@doctrinebot commented on GitHub (Jan 25, 2010):

Comment created by @beberlei:

@Guilherme - That was because of the your latest commit on additional entity class information :-)

I guess the way to go (and i already initiazed first contact) is to patch the Reflection C API in PHP to show the class name instead.

@doctrinebot commented on GitHub (Jan 25, 2010): Comment created by @beberlei: @Guilherme - That was because of the your latest commit on additional entity class information :-) I guess the way to go (and i already initiazed first contact) is to patch the Reflection C API in PHP to show the class name instead.
Author
Owner

@doctrinebot commented on GitHub (Apr 12, 2010):

Comment created by @guilhermeblanco:

That's a PHP issue, as Benjamin stated. Patch already submitted to PHP core team.

Cheers,

@doctrinebot commented on GitHub (Apr 12, 2010): Comment created by @guilhermeblanco: That's a PHP issue, as Benjamin stated. Patch already submitted to PHP core team. Cheers,
Author
Owner

@doctrinebot commented on GitHub (Apr 12, 2010):

Issue was closed with resolution "Fixed"

@doctrinebot commented on GitHub (Apr 12, 2010): Issue was closed with resolution "Fixed"
Author
Owner

@doctrinebot commented on GitHub (Dec 13, 2015):

Imported 1 attachments from Jira into https://gist.github.com/945b1db15562118749d6

@doctrinebot commented on GitHub (Dec 13, 2015): Imported 1 attachments from Jira into https://gist.github.com/945b1db15562118749d6 - [10311_CliController_Exception.patch](https://gist.github.com/945b1db15562118749d6#file-10311_CliController_Exception-patch)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#333