Bug #50077 for TryCatch: Bug with TryCatch and XML::SAX::Expat: Try Catch Internal Error: ENTERTRY op did not have VOID context (it was 0)

Mon Sep 28 16:29:36 2009 bob [...] cakebox.net - Ticket created

Subject:	Bug with TryCatch and XML::SAX::Expat: Try Catch Internal Error: ENTERTRY op did not have VOID context (it was 0)
Date:	Mon, 28 Sep 2009 22:28:25 +0200
To:	bug-TryCatch [...] rt.cpan.org
From:	Knut Arne Bjørndal <bob [...] cakebox.net>

Download smime.p7s
application/x-pkcs7-signature 4k

Message body not shown because it is not plain text.

Hi Seems there's a bug in TryCatch or XML::SAX::Expat that causes it to abort with "Try Catch Internal Error: ENTERTRY op did not have VOID context (it was 0)" when used together with XML::SAX::Expat. I'm attaching a test case that on my system (up to date debian sid as of yesterday, perl 5.10.0, TryCatch 1.002000, XML::SAX::Expat 0.40) outputs the following: caught message caught message Try Catch Internal Error: ENTERTRY op did not have VOID context (it was 0) Aborted I'm off now to replace TryCatch with the slightly less magical Exception::Class catch handling, so I can get something done on this project, but I'll be happy to provide further debugging information if you need any. -- Knut Arne Bjørndal aka Bob Kåre bob@cakebox.net http://bob.cakebox.net/

Message body is not shown because sender requested not to inline it.

Mon Sep 28 16:42:56 2009 ash_rtcpan [...] firemirror.com - Correspondence added

On Mon Sep 28 16:29:36 2009, bob@cakebox.net wrote: Show quoted text

> Hi > > Seems there's a bug in TryCatch or XML::SAX::Expat that causes it to > abort with "Try Catch Internal Error: ENTERTRY op did not have VOID > context (it was 0)" when used together with XML::SAX::Expat. > > I'm attaching a test case that on my system (up to date debian sid as > of yesterday, perl 5.10.0, TryCatch 1.002000, XML::SAX::Expat 0.40) > outputs the following: > > caught message > caught message > Try Catch Internal Error: ENTERTRY op did not have VOID context (it

was 0) Show quoted text

> Aborted > > I'm off now to replace TryCatch with the slightly less magical > Exception::Class catch handling, so I can get something done on this > project, but I'll be happy to provide further debugging information if > you need any. >

Damn. Thanks for reporting this and not just silently replacing it. I will have a look at this.

Mon Sep 28 16:42:57 2009 The RT System itself - Status changed from 'new' to 'open'

Fri Apr 22 18:12:21 2011 ash_rtcpan [...] firemirror.com - Correspondence added

I fixed this with v1.03000 - just forgot about this bug so didn't resolve it then. (And I've just added this as a test case to the repo)

Fri Apr 22 18:12:22 2011 ash_rtcpan [...] firemirror.com - Status changed from 'open' to 'resolved'