In our code at work (mostly C++, no Perl) someone put something in to try to write a stack trace to a log by intercepting windows structured exceptions. This makes debugging stack and heap corruption issues more difficult, IMO. The stack trace we manage to write is almost always nonsense for memory problems. What I want generally when debugging is a memory dump I can look at with windbg with as few operations attempted as possible since the corruption happened. i.e. I want an abort(). Whoever wrote MS's new functions like strcpy_s seems to agree, though they give you a way to override the behaviour: CRT Parameter Validation.

In reply to Re: Win32::API, sees C stack corruption, failure mode ideas by thirdm
in thread Win32::API, sees C stack corruption, failure mode ideas by bulk88

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.