Bug 484668 – x11-libs/pango-1.30.1 - Command '['.../work/pango-1.30.1/pango/tmp-introspect52mPX7/PangoFT2-1.0', '--introspect-dump=.../functions.txt,.../dump.xml']' returned non-zero exit status -11

• Status: RESOLVED TEST-REQUEST
• Product: Gentoo Linux

[Description Alexey Badyaev 2013-09-12 12:28:28 UTC]

Created attachment 358534 [details]
The complete build log

Command '['/tmp/portage/x11-libs/pango-1.30.1/work/pango-1.30.1/pango/tmp-introspect52mPX7/PangoFT2-1.0', '--introspect-dump=/tmp/portage/x11-
libs/pango-1.30.1/work/pango-1.30.1/pango/tmp-introspect52mPX7/functions.txt,/tmp/portage/x11-libs/pango-1.30.1/work/pango-1.30.1/pango/tmp-in
trospect52mPX7/dump.xml']' returned non-zero exit status -11
make[4]: *** [PangoFT2-1.0.gir] Error 1
make[4]: Leaving directory `/tmp/portage/x11-libs/pango-1.30.1/work/pango-1.30.1/pango'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/tmp/portage/x11-libs/pango-1.30.1/work/pango-1.30.1/pango'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/tmp/portage/x11-libs/pango-1.30.1/work/pango-1.30.1/pango'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/portage/x11-libs/pango-1.30.1/work/pango-1.30.1'
make: *** [all] Error 2
 * ERROR: x11-libs/pango-1.30.1::gentoo failed (compile phase):
 *   emake failed

[Comment 1 Alexey Badyaev 2013-09-12 12:29:00 UTC]

Created attachment 358536 [details]
The ebuild environment file

[Comment 2 Alexey Badyaev 2013-09-12 12:29:33 UTC]

Created attachment 358538 [details]
the output of `emerge --info '=x11-libs/pango-1.30.1::gentoo'`

[Comment 3 Alexey Badyaev 2013-09-12 12:29:56 UTC]

Created attachment 358540 [details]
the output of `emerge -pqv '=x11-libs/pango-1.30.1::gentoo'`

[Comment 4 Alexandre Rostovtsev (RETIRED) 2013-09-13 15:51:04 UTC]

Please install app-admin/abrt, start it (/etc/init.d/abrt start), get pango to fail to emerge, and get a backtrace of the PangoFT2-1.0 crash using abrt-gui or abrt-cli.

Please attach the backtrace here.

[Comment 5 Alexey Badyaev 2013-09-14 13:58:16 UTC]

Created attachment 358642 [details]
backtrace of the PangoFT2-1.0 crash

[Comment 6 Alexandre Rostovtsev (RETIRED) 2013-09-14 16:15:56 UTC]

Interesting, doesn't seem to be nvidia-related after all.

Does updating to pango-1.32.5 work? (you mentioned in the other bug that you are using glib-2.34 and gobject-introspection-1.34, which are from the same gnome release as pango-1.32; but pango-1.30 was released 6 months before that, with gobject-introspection-2.32).

[Comment 7 Alexey Badyaev 2013-09-16 05:40:16 UTC]

Updating to pango-1.32.5 do not work - with the same result. I attach new crash-report to this issue.

[Comment 8 Alexey Badyaev 2013-09-16 05:41:01 UTC]

Created attachment 358762 [details]
Backtrace of the pango-1.32.5 build crash.

[Comment 9 Alexandre Rostovtsev (RETIRED) 2013-09-16 13:21:41 UTC]

(In reply to Alexey Badyaev from comment #8)

> warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.

Please re-emerge sys-libs/glibc and dev-libs/glib with debugging flags (meaning: CFLAGS="-O2 -march=pentium4 -pipe -ggdb", CXXFLAGS="-O2 -march=pentium4 -pipe -ggdb", and also add "splitdebug" to FEATURES in make.conf), try building pango with the debugging flags, and obtain the backtrace again?

When the whole system was built with "-fomit-frame-pointer" and no debugging information, gdb and abrt can't tell in which library the crash is occurring.

[Comment 10 Alexey Badyaev 2013-09-17 04:27:13 UTC]

Created attachment 358846 [details]
Backtrace of the pango-1.32.5

I did: re-emerge sys-libs/glibc and dev-libs/glib with debugging flags
(meaning: CFLAGS="-O2 -march=pentium4 -pipe -ggdb", CXXFLAGS="-O2
-march=pentium4 -pipe -ggdb", and also add "splitdebug" to FEATURES in
make.conf), try building pango with the debugging flags, and obtain the
backtrace again.

[Comment 11 Alexandre Rostovtsev (RETIRED) 2013-09-17 12:39:32 UTC]

Thanks, this is at least something.

Judging by the addresses, #2 is libgmodule, #1 is libdl (so we can surmise that this is libgmodule loading a module or plugin), but #0 (the module where the crash occurs, and the place that we are interested in) is unknown :/

[Comment 12 Pacho Ramos 2013-12-24 13:34:02 UTC]

Please try with 1.34.1

[Comment 13 Alexey Badyaev 2013-12-25 03:19:41 UTC]

I try with 1.34.1, and problem disappear now!