|
I have a bug in some code that uses ALCHSS.
One pgm uses ALCHSS to allocate entries for a
linked list, later on another pgm reads the list entries and is randomly
receiving some bad data. So far 8 hours into the bug hunt and no sign of a
culprit.
I allocate from the default heap space. The
ALCHSS stmt looks like this:
ALCHSS pData, 0, nSize
;
Any known or suspected problems with ALCHSS?
The MI manual says the "creation size
advisory is 4KB". Most of the allocations I do are much smaller than that
(although the ones with the bug are little less than 4096). Any ideas on why the
advisory?
Any reason to think that ALCHSS is not rock
solid? I would guess that ile uses it extensively.
A debugger feature plea: When in debug
mode, provide an "AddAddrBkp" cmd. When an address range is referenced
in the job being debugged, call a debug handler pgm. Similar to the action
of the breakpoint handing pgm that is called when an instruction is executed.
Thanks,
Steve Richter
|
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.