problem with XML::Parser dying on errors...

[Bruno Boettcher]

hello!

i have a little daemon which fetches regularly some rss feeds, now for
some time that daemon keeps crashing on me with the message:
not well-formed (invalid token) at line 80, column 45, byte 4904 at
/usr/lib/perl5/XML/Parser.pm line 187
from the cpan shell:
XML:arser is up to date (2.34).

i mean i would like to deal with the error myself, e.g. spit out the
data that caused that error... but at the moment i seem unable to stop
XML:arser or expat to die on my with no usable info on what is going
wrong....

anyway since that thing is supposed to be a daemon, i can't have modules
dying nad compromising the whole functionality...
is there any way to stop it from doing that?

 

[xhoster]

hello!

i have a little daemon which fetches regularly some rss feeds, now for
some time that daemon keeps crashing on me with the message:
not well-formed (invalid token) at line 80, column 45, byte 4904 at
/usr/lib/perl5/XML/Parser.pm line 187
from the cpan shell:
XML:arser is up to date (2.34).

i mean i would like to deal with the error myself, e.g. spit out the
data that caused that error... but at the moment i seem unable to stop
XML:arser or expat to die on my with no usable info on what is going
wrong....

You trap XML:arser dies the same way you trap any other dies in Perl,
by using eval BLOCK. See perldoc -f eval. Once you trap the die, I don't
know how you get the data which caused it in a nice format for printing.
Perhaps you should pass your data through a validator before giving it to
XML:arser.

Xho

 

[Tad McClellan]

not well-formed (invalid token) at line 80, column 45, byte 4904 at
/usr/lib/perl5/XML/Parser.pm line 187
from the cpan shell:
XML:arser is up to date (2.34).

i mean i would like to deal with the error myself, e.g. spit out the
data that caused that error... but at the moment i seem unable to stop
XML:arser or expat to die on my with no usable info on what is going
wrong....

anyway since that thing is supposed to be a daemon, i can't have modules
dying nad compromising the whole functionality...
is there any way to stop it from doing that?

You use "eval BLOCK" to handle exceptions in Perl.