comment on

A slight translation may help (but probably not). the 'instruction at "0x77c46fa3"' bit means that an instrustion at that (run time) address. If you can get a symbol dump of the code you can in principle find the (machine language) instruction that is causeing the trouble and should be able to identify the routine that is involved. A much more useful thing generally is to get a stack dump so you can figure out somthing of the context of the failure. You should be able to get at least a partial stack dump from the System Event Viewer.

The 'memory could not be "read"' means an invalid access. The instruction was trying to access memory that the process doesn't own. Normally that means a bad pointer - either uninitialised, or trashed in some fashion. It may be an access beyond the end of an array for example.

What version of Perl and can you post some code that you implicate in generating the problem? How often does it happen?

DWIM is Perl's answer to Gödel

In reply to Re: Win32 - Memory can not be "read" by GrandFather
in thread Win32 - Memory can not be "read" by HuckinFappy

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.


Syntactic Confectionery Delight
	PerlMonks