Thanks Tom.
Yeah for XML::Parser line 236 perhaps we can get Clark (Current maintainer
according to POD) to change it to
return undef if $err;
Mark.
ps: I'll check that rule (tommorow. ..must...have...sleep..)
Tom Harper wrote:
Mark--
While you may be having problems with segfaults because
[EMAIL PROTECTED] (Matt Sergeant) wrote:
On Fri, 4 May 2001, Perrin Harkins wrote:
on 5/4/01 9:28 AM, Mark Maunder at [EMAIL PROTECTED] wrote:
I have an Apache::Registry script that is using XML::Parser. The
parser throws a 'die' call if it encounters a parse error (Why?).
Because it's an
Hi,
I'm sure this has been discussed, appologies if it has, but I scoured the lists
and docs and didn't get any help.
I have an Apache::Registry script that is using XML::Parser. The parser throws a
'die' call if it encounters a parse error (Why?). I was handling this by putting
the code in an
On Fri, 4 May 2001, Mark Maunder wrote:
Hi,
I'm sure this has been discussed, appologies if it has, but I scoured the lists
and docs and didn't get any help.
I have an Apache::Registry script that is using XML::Parser. The parser throws a
'die' call if it encounters a parse error (Why?).
on 5/4/01 9:28 AM, Mark Maunder at [EMAIL PROTECTED] wrote:
I have an Apache::Registry script that is using XML::Parser. The parser throws
a
'die' call if it encounters a parse error (Why?).
Because it's an exception and the parser can't continue.
I was handling this by
putting
the code
OK this is a little embarrasing... I assumed the script was die'ing when it hit the
XML::Parser routine and that eval wasn't catching the exception. Well the Apache
child is actually segfaulting. (Excuse: I'm running virtual hosts with seperate
logs. I didn't check the main error_log.). I checked
Mark--
While you may be having problems with segfaults because
of expat = yes rule-- i was having similar problems
with XML parser relating to the the die statement.
I do the same thing as far as eval'ing the parsefile
call. Also, I removed the die statement from parser.pm
(v 2.29 line 240
