Re: segmentation fault trying to use Pan 0.146:my LOCALE settings

On 2019-12-01 15:46, Julien Michielsen wrote:
> Rhialto schreef op 01-12-2019 15:12:
>> On Sun 01 Dec 2019 at 14:41:25 +0100, Per Hedeland wrote:
>>> > Does anyone have a hint how to get this running?
>>>
>>> Not me - FWIW, Pan 0.145 works fine for me on FreeBSD. It may be
>>> something specific to your environment. Does it crash immediately on
>>> startup, i.e. doesn't even display a window? If not, how far does it
>>> get?
>>
>> My guess it is something locale-related. I had problems when I tried to
>> run Pan in a non-UTF-8 locale. It would try to do something with "smart
>> quotes" and fail and get a NULL pointer. Maybe something like that could
>> be going on here.

It certainly seems to be *somehow* locale-releated - Pan is about to
print the date of an article, and it seems the NUL *may* be the result
of this call:

   locale_this_year = g_locale_from_utf8 (_("%b %d %l∶%M %p"), -1, NULL, NULL, NULL);

For some reason, the thing between %l and %M, which may or may not
look like a colon to you, is actually "Unicode Character 'RATIO'
(U+2236)" instead of a normal ascii ':'. The g_locale_from_utf8()
function (in glib) "Converts a string from UTF-8 to the encoding used
for strings by the C runtime (usually the same as that used by the
operating system) in the current locale.", may return NULL on failure,
and Pan doesn't check for this. It's conceivable that it will fail in
som cases, but...

> my locale, would anyone be able to see something that is not accepted
> by pan?
> 
> LANG=nl_NL.UTF-8@euro
> LANGUAGE=
> LC_CTYPE="C"
> LC_NUMERIC="C"
> LC_TIME="C"
> LC_COLLATE="C"
> LC_MONETARY="C"
> LC_MESSAGES="C"
> LC_PAPER="C"
> LC_NAME="C"
> LC_ADDRESS="C"
> LC_TELEPHONE="C"
> LC_MEASUREMENT="C"
> LC_IDENTIFICATION="C"
> LC_ALL=C

...this doesn't look like anything out of the ordinary. AFAIR, LC_ALL
should override LANG, but maybe not in all cases... The LANGUAGE=
i.e. set to nothing, looks a bit suspcious, but I'm not sure what the
rules are for that variable. You could try starting Pan with

env LANG=C pan

and see if it helps. If not, try also 'unset LANGUAGE' (assuming
sh-style shell) before that. (Personally I don't have any locale
settings, which should be the same as "C".)

--Per

_______________________________________________
Pan-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/pan-users