On Sun, May 14, 2023 at 5:34 AM Sven Schreiber <sven.schreiber(a)fu-berlin.de&gt; wrote: > > Hi, > > this is with the April 19th snapshot on Windows 10 (running in German without local comma), and is reproducible. > > - open the package list window via the button at the bottom > > - search for the StrucBreak package by entering "struc" in the search field - I'm seeing v0.91 here, from 2021 > > - right-click on the entry, and select "view code" - after a few seconds, gretl is closed/crashing; but no message from the OS about it I can confirm that, and I'm seeing this:

Am 14.05.2023 um 16:07 schrieb Cottrell, Allin: > I can confirm that, and I'm seeing this: > > ' matrices c...' > *** buffer overflow detected ***: terminated > Aborted (core dumped) > > It's due to the massively long statements defining arrays of > critical-value matrices. A fix should be forthcoming shortly, but I > don't think such statements are the right way to store big matrices. > Better to put them into .bin matrix files and load them on demand. Well, maybe. I admit it was a lazy solution (copied over from the original Ox code), but apart from the fact that it has "just worked", the advantage is that a user can inspect those tables quite easily. If we store the tables as bin matrices, it seems to me we would hide them away. Of course, in principle we could reproduce them in the help doc. Or would there be another way of making them accessible - I mean apart from telling people to manually poke around the directory where the file is stored and then using mread() ?