misc/148450: recent glib20 __STDC_ISO_10646__ fix causes pidgin to
crash
Kyryll A Mirnenko
xmirya at gmail.com
Thu Jul 8 11:30:04 UTC 2010
>Number: 148450
>Category: misc
>Synopsis: recent glib20 __STDC_ISO_10646__ fix causes pidgin to crash
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Jul 08 11:30:03 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Kyryll A Mirnenko
>Release: RELENG_8_1
>Organization:
>Environment:
FreeBSD notebook 8.1-RC2 FreeBSD 8.1-RC2 #7: Wed Jul 7 23:22:36 EEST 2010 root at miryanote:/usr/src/sys/i386/compile/MY-LITE i386
>Description:
I've got devel/glib20 built WITH_COLLATION_FIX=yes . The last commit to devel/glib20/Makefile adds a __STDC_ISO_10646__ definition to configure arguments for that option. The problem is pidgin (net-im/pidgin) constantly crashes if all conditions below are met:
a) glib20 built WITH_COLLATION_FIX=yes
b) glib20 built after that commit (so with __STDC_ISO_10646__ definition)
c) pidgin is started with uk_UA.KOI8-U locale
, but works well when any of three requirements above is lifted, e.g. if i reset locale to C, or if the commit is reverted (as it was before) it works well.
According to the `pidgin -d` log the crash occurs somewhere during constructing the buddy list (either read from the local configuration in ~/.purple or after an account added and the server contact list is read when started from scratch with no ~/.purple existing).
Also, the possible significant condition is that the buddylist contains non-latin group names (while buddy names are all latin)
>How-To-Repeat:
>Fix:
Revert the __STDC_ISO_10646__ definition commit
or
unset devel/glib20 WITH_COLLATION_FIX=yes option
or
run an application (pidgin) with C locale
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list