Ok, you are correct. I had missed that, hmm... I guess a next question is whether any of the other memory audit mechanisms need to be moved to be before or after that line 1485 test (or whether they need to be changed to account for the fact that the memory they are inspecting might not be J allocated memory).
But I guess I also need to be thinking about other possible causes of the error I'm trying to track down. (For example: is it possible that something in the threading code assumes something about representations for extended integers? This seems incredibly unlikely, but gmp memory might not be following the rules for allocation sizes, and I'm not sure I understand that aspect of the implementation.) Anyways, it's clear that I need to do more work on tracking down this issue. Thanks, -- Raul On Sat, Nov 11, 2023 at 9:33 AM Henry Rich <[email protected]> wrote: > > I thought that jtmf inspects the header and vectors to your gmp code to > free it (line 1485). jtmf accepts any A block, including A blocks in > indirect values, but it does the free only on blocks it allocated. > > Going away for 1-2 hours, > > hhr > > On 11/11/2023 9:28 AM, Raul Miller wrote: > > Hmm... > > > > My thinking was that jtmf was the implementation for the mf() macro > > which the mfgmp() macro is parallel to. > > > > This corresponds also to the structure and use of frcommon(). > > > > So I guess my question to you is: jtmf is capable of safely freeing > > gmp allocated memory, what's the point of the frcommon() macro (and > > the fr() and frgmp() macros which rely on it)? > > > > Thanks, > > > > > > -- > > Raul > > > > > > > > On Sat, Nov 11, 2023 at 9:19 AM Henry Rich <[email protected]> wrote: > >> But it was flagged that way in the block, no? So it should be be freed > >> by the gmp allocator. > >> > >> > >> hhr > >> > >> On 11/11/2023 9:16 AM, Raul Miller wrote: > >>> The free was memory which had not been allocated by J's memory > >>> allocation process. > >>> > >> ---------------------------------------------------------------------- > >> For information about J forums see http://www.jsoftware.com/forums.htm > > ---------------------------------------------------------------------- > > For information about J forums see http://www.jsoftware.com/forums.htm > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
