comment on

First of all, the interpreter doesn't crash "@$miDoc->{Images}->Item(0)->{Layout}{Text}", it crashes "at $miDoc...". The difference is important, as the '@' character could easily be part of code. By correctly spelling the word 'at' and using <code> tags your question would be made clearer.

How do you know it crashes there? The only relevant-looking diagnostics I can see are three lines earlier (your die) and a coupla lines later when you write to the log file.

Why the inconsistent use (and non-use) of -> in that line? That indicates to me that you may be merely cutting and pasting bits of code without any understanding of what you're doing, in which case it's much harder to help you.

What EXACTLY are the error messages you're seeing? And are you using strict and warnings?

In reply to Re: Perl intepreter crash when tyring to get the text from OCRed output by DrHyde
in thread Perl intepreter crash when tyring to get the text from OCRed output by priyaviswam

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Come for the quick hacks, stay for the epiphanies.
	PerlMonks