[Info-vax] ACCVIO using calloc in C on VMS 8.3 Alpha

[seasoned_geek]

I would suggest they compile ALL of their source code with /CHECK and
fix what it flags.

If that doesn't clear up the problem, THEN and ONLY THEN, we need to
see what the UAF settings are for your account.  If you have
absolutely no privs and have very small working set/page file quota/
etc. you could legitimately get this error having done nothing
wrong...other than use more RAM than your account is allowed.

On Jul 30, 7:49 am, Tom Dahl <nikond... at gmail.com> wrote:
> I agree with Bob that a likely explanation is that something in the
> application has corrupted LIBRTL's heap data structures -- e.g., freed
> a block of memory twice in succession, or written into a block that
> has been freed (LIBRTL uses the first few bytes of freed blocks for
> internal book-keeping purposes), or outright writing where it
> shouldn't have written.
>
> The Heap Analyzer (HA) can be handy to find invalid heap usage
> sequences. Check the VMS documentation for how to enable and use it
> (or search the web).