Re: [Gretl-users] gretl crashed while searching for file
On Wed, 13 Feb 2019, Fred Engst wrote:
>> [...]
>> Attached is the crash report if it helps.
And I replied:
> Thanks, I've looked into this, but I'm still stumped.
>
> Taking my cue from your "I have Chinese on my system also" I created
> a Desktop directory with Chinese characters in its name, and put in
> there a gretl data file with Chinese characters in its name -- on a
> Macbook Air running OS X 10.10.5. Then I tried opening the data file
> in question via "/File/Open data/User file..." And the file opened
> without any problem. [...]
>
> If you're able to give us any more information about the exact
> context of, or sequence of events leading up to, the crash, please
> do!
Fred now adds:
Hi Allin,
Thanks for trying.
I’m not sure why gretl keeps crashing on my Mac when I do a search
within gretl. I tried log onto my administrative account and it
crashes just the same. I tried to invoke an earlier version of
gretl (1.9.11) but failed to make it work, after I have downloaded
and installed GTK and XQuartz.
I then installed instead version 2016d which I have and it crashes
just the same.
Since my os has a lot of quirky behaviours, lets not worry too
much about my crash unless others report the same.
Thanks, Fred, your experiments go above and beyond the call of duty!
I'll just lay down one marker in case this issue comes up for
others. The Apple crash report gives as the reason for the "uncaught
exception"
Conversion to encoding 30 failed for string "/Volumes/FredMacHD/U..."
(where the ellipsis is in the original).
If OS X uses UTF-8 (as does GTK), why would any conversion be
needed? (And what's "encoding 30"? I couldn't track that down.)
Ah well, it turns out there's UTF-8 and UTF-8. The Mac HFS+
filesystem uses NFD (Normalization Form canonical Decomposition) for
filenames while the rest of the world uses NFC (Normalization Form
canonical Composition). So I guess something is going wrong
converting from one of these forms of UTF-8 to the other.
In my first reply to Fred I said I thought this might be a GTK bug.
At present I'm more inclined to think it's an Apple bug. But I'm out
of my depth in this area; regretfully I'm going to treat it as an
unexplained anomaly for now.
Allin