On Thu, Jan 03, 2008 at 07:20:38AM -0800, Ovid wrote:
> We couldn't reproduce the segfaults in the debugger or with
> Devel::Trace, but after a lot of work, a colleague and I found the
> culprit: Contextual::Return. Like Sub::Uplevel, it overrides
> CORE::GLOBAL::caller.
That probably explains
On Jan 3, 2008 11:09 AM, Ovid <[EMAIL PROTECTED]> wrote:
> For smaller projects, you have fewer interactions. For large projects,
> globally altered behavior is playing russian roulette without counting
> the bullets.
At least Sub::Uplevel documentation makes a point of warning in
several places
--- David Golden <[EMAIL PROTECTED]> wrote:
> Maybe it's too late, but which versions of Sub::Uplevel and
> Contextual::Return were you using?
Sub::Uplevel 0.12 (and old version. Forgot to check that).
Contextual::Return was 0.2.1 both with and without the patch listed in
http://rt.cpan.org/Publ
On Jan 3, 2008 10:20 AM, Ovid <[EMAIL PROTECTED]> wrote:
> We couldn't reproduce the segfaults in the debugger or with
> Devel::Trace, but after a lot of work, a colleague and I found the
> culprit: Contextual::Return. Like Sub::Uplevel, it overrides
> CORE::GLOBAL::caller. Apparently the two do
My test aggregation took a bit longer to implement than Adrian's due to
several issues. Some were bugs in tests, some were in code, but one
issue which took a *long* time to debug was random segfaults.
We couldn't reproduce the segfaults in the debugger or with
Devel::Trace, but after a lot of wo
