On Thu, 19 Jun 2025 11:46:18 -0700, Leonard D Woren <[email protected]> wrote:
>Charles Mills wrote on 6/18/2025 1:19 PM: >> Well, it looks like the worst possible outcome. The problem simply went away. > >"Problems that go away by themselves come back by themselves." -- >very old saying. Indeed. Further update. The problem did not totally go away. But it moved from this horrible gigantic incomprehensible dump to a manageable S0C1. Not easy to get a S0C1 in a higher level language but it turned out that a storage overlay was corrupting the function table that lets code invoke an object's methods, leading to the S0C1. It took a while to find the cause of the storage overlay, but it turned out to be -- of course -- stupid programmer error. I was double deleting -- deleting twice -- an object on the heap. Now if would be nice if a higher-level language running in a debug sort of mode would diagnose a double-delete rather than overlaying unrelated storage ... but there are many things in this world that would be nice. Thanks again all for your suggestions. Charles ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
