glibmm2.4 version 2.29.11-0ubuntu1 failed to build in oneiric

Bug #829596 reported by Matthias Klose
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
glibmm2.4 (Ubuntu)
Fix Released
High
Unassigned
Oneiric
Fix Released
High
Unassigned

Bug Description

glibmm2.4 version 2.29.11-0ubuntu1 failed to build in oneiric
Link to failed build: https://launchpad.net/ubuntu/+archive/test-rebuild-20110816/+build/2694192

Details about the rebuild:
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110816-oneiric.html

Direct link to the build log: https://launchpad.net/ubuntu/+archive/test-rebuild-20110816/+build/2694192/+files/buildlog_ubuntu-oneiric-amd64.glibmm2.4_2.29.11-0ubuntu1_FAILEDTOBUILD.txt.gz

This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'.
Excerpt 1860 lines into the build log:

PASS: glibmm_null_containerhandle/test
/bin/bash: line 5: 27205 Segmentation fault ${dir}$tst
FAIL: glibmm_refptr_sigc_bind/test
=======================================================================
1 of 19 tests failed
Please report to http://bugzilla.gnome.org/enter_bug.cgi?product=glibmm
=======================================================================
make[3]: *** [check-TESTS] Error 1
make[3]: Leaving directory `/build/buildd/glibmm2.4-2.29.11/tests'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory `/build/buildd/glibmm2.4-2.29.11/tests'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/build/buildd/glibmm2.4-2.29.11'
make: *** [debian/stamp-makefile-check] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
******************************************************************************
Build finished at 20110817-0253
FAILED [dpkg-buildpackage died]
Purging chroot-autobuild/build/buildd/glibmm2.4-2.29.11

Tags: ftbfs oneiric
Matthias Klose (doko)
Changed in glibmm2.4 (Ubuntu):
milestone: none → ubuntu-11.10-beta-1
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Steve Langasek (vorlon) wrote :

Backtrace suggests this might be a libsigc++ problem?

Program received signal SIGSEGV, Segmentation fault.
sigc::internal::trackable_callback_list::~trackable_callback_list (
    this=0x604050, __in_chrg=<optimized out>) at ../../sigc++/trackable.cc:89
89 if ((*i).func_)
(gdb) bt
#0 sigc::internal::trackable_callback_list::~trackable_callback_list (
    this=0x604050, __in_chrg=<optimized out>) at ../../sigc++/trackable.cc:89
#1 0x00007ffff7bd9651 in sigc::trackable::notify_callbacks (this=0x604170)
    at ../../sigc++/trackable.cc:67
#2 0x00007ffff7bd9ab3 in ~slot_rep (this=0x604170, __in_chrg=<optimized out>)
    at ../../sigc++/functors/slot_base.h:87
#3 sigc::slot_base::~slot_base (this=<optimized out>,
    __in_chrg=<optimized out>) at ../../sigc++/functors/slot_base.cc:101
#4 0x00007ffff7bd921c in destroy (__p=0x604150, this=<optimized out>)
    at /usr/include/c++/4.6/ext/new_allocator.h:118
#5 _M_erase (__position=..., this=<optimized out>)
    at /usr/include/c++/4.6/bits/stl_list.h:1537
#6 erase (__position=..., this=<optimized out>)
    at /usr/include/c++/4.6/bits/list.tcc:113
#7 sigc::internal::signal_impl::sweep (this=0x604120)
    at ../../sigc++/signal_base.cc:75
#8 0x00007ffff7bd9255 in sigc::internal::signal_impl::notify (
    d=<optimized out>) at ../../sigc++/signal_base.cc:84
#9 0x00007ffff7bd9a5f in sigc::internal::slot_rep::notify (data=0x604170)
    at ../../sigc++/functors/slot_base.cc:63
#10 0x00007ffff7bd95d7 in sigc::internal::trackable_callback_list::~trackable_callback_list (this=0x6040d0, __in_chrg=<optimized out>)
    at ../../sigc++/trackable.cc:90
#11 0x00007ffff7bd9651 in sigc::trackable::notify_callbacks (this=0x604010)
    at ../../sigc++/trackable.cc:67
#12 0x0000000000401625 in ~Test (this=0x604010, __in_chrg=<optimized out>)
    at glibmm_refptr_sigc_bind/main.cc:47
#13 main () at glibmm_refptr_sigc_bind/main.cc:65
(gdb) print i
$1 = {_M_node = 0x0}
(gdb)

Revision history for this message
Murray Cumming (murrayc) wrote :

Yes, it's a fail in a new test, that requires the latest libsigc++. I (upstream) will change configure.ac to check for that. In the meantime (and later anyway), you'll need to update libsigc++.

There's more about it in the ChangeLog.

Revision history for this message
Sebastien Bacher (seb128) wrote :

ok, mvo updated the lib, I will retry this one once the binaries are published

Changed in glibmm2.4 (Ubuntu Oneiric):
status: Confirmed → Fix Committed
Changed in glibmm2.4 (Ubuntu Oneiric):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.