Bug #14443 for Test-MockObject: Interactions with UNIVERSAL::can results in debugger explosions

Sat Sep 03 13:46:06 2005 adamk [...] cpan.org - Ticket created

Subject:

Interactions with UNIVERSAL::can results in debugger explosions

For some reason, Test::MockObject behaves differently in the debugger to normal code. This would seem to be due to some strange interaction and feedback with UNIVERSAL::can. It falsely throws the following Called UNIVERSAL::can() as a function, not a method at ../lib/Test/MockObject.pm line 118 UNIVERSAL::can::can() called at ../lib/Test/MockObject.pm line 118 Test::MockObject::__ANON__[../lib/Test/MockObject.pm:119]() called at ../lib/Test/MockObject/Extends.pm line 90 Test::MockObject::Extends::__ANON__[../lib/Test/MockObject/Extends.pm:108]() called at t/extends.t line 57 In combination with Test::Warn, this results in all tests dying, and makes it extraordinarily difficult to do debugging of test scripts.

Sat Dec 24 04:36:49 2005 chromatic [...] cpan.org - Status changed from 'new' to 'open'

Sat Dec 24 04:36:49 2005 chromatic [...] cpan.org - Given to CHROMATIC

Sat Mar 04 18:58:22 2006 chromatic [...] cpan.org - Correspondence added 20 min

This appears to be a problem with the debugger and its interaction with caller(), in that when the debugger is active, the call stack doesn't seem to contain the *__ANON__ glob for the name of anonymous subroutines. I'll report this to p5p in a moment.

Sat Mar 04 18:58:24 2006 chromatic [...] cpan.org - Status changed from 'open' to 'resolved'

Sun Apr 09 02:05:19 2006 chromatic [...] cpan.org - Correspondence added 30 min

I fixed this in version 1.05 and added a test so it should never reoccur.

Sun Apr 09 02:05:19 2006 The RT System itself - Status changed from 'resolved' to 'open'

Sun Apr 09 02:05:59 2006 chromatic [...] cpan.org - Status changed from 'open' to 'resolved'