Bug #123747 for threads: Exception objects are obfuscated

Sun Nov 26 00:25:28 2017 XENU [...] cpan.org - Ticket created

Subject:

Exception objects are obfuscated

Show quoted text

> perl -MException::Class=foobar -Mthreads -E '$t = threads->create(sub { foobar->throw } ); $t->join; say $t->error'

Thread 1 terminated abnormally: main=HASH(0x4df6eb0) at -e line 1. [Generic exception] If it's technically impossible to copy the real exception object to the parent thread, then maybe stringifing it would be more sensible?

Mon Nov 27 15:57:40 2017 jdhedden [...] cpan.org - Correspondence added

On 2017-11-26 00:25:28, XENU wrote: Show quoted text

> > perl -MException::Class=foobar -Mthreads -E '$t = threads->create(sub > > { foobar->throw } ); $t->join; say $t->error'

> Thread 1 terminated abnormally: main=HASH(0x4df6eb0) at -e line 1. > [Generic exception] > > If it's technically impossible to copy the real exception object to > the parent thread, then maybe stringifing it would be more sensible?

The exception object is returned to the parent: $t->error As such, while I agree the error object is not stringified in the warning message, there isn't a compelling need to modify the existing XS code to do such.

Mon Nov 27 15:57:40 2017 The RT System itself - Status changed from 'new' to 'open'

Mon Nov 27 15:57:40 2017 jdhedden [...] cpan.org - Status changed from 'open' to 'rejected'