seed version 3.0.0-2 failed to build in oneiric

Bug #831143 reported by Matthias Klose
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
seed (Ubuntu)
Fix Released
High
Unassigned
Oneiric
Fix Released
High
Unassigned

Bug Description

seed version 3.0.0-2 failed to build in oneiric
Link to failed build: https://launchpad.net/ubuntu/+source/seed/3.0.0-2/+build/2622587

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/+source/seed/3.0.0-2/+build/2622587/+files/buildlog_ubuntu-oneiric-amd64.seed_3.0.0-2_FAILEDTOBUILD.txt.gz

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

make[5]: Entering directory `/build/buildd/seed-3.0.0/doc/modules/readline'
../../../src/seed ../../../doc/modules/make-functions.js ../../../doc/modules/readline/readline.js > ../../../doc/modules/readline/readline-funcs.xml
/bin/bash: line 1: 8542 Segmentation fault ../../../src/seed ../../../doc/modules/make-functions.js ../../../doc/modules/readline/readline.js > ../../../doc/modules/readline/readline-funcs.xml
make[5]: *** [readline-funcs.xml] Error 139
make[5]: Leaving directory `/build/buildd/seed-3.0.0/doc/modules/readline'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/build/buildd/seed-3.0.0/doc/modules'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/build/buildd/seed-3.0.0/doc'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/build/buildd/seed-3.0.0'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/build/buildd/seed-3.0.0'
make: *** [debian/stamp-makefile-build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
******************************************************************************
Build finished at 20110712-1940
FAILED [dpkg-buildpackage died]
Purging chroot-autobuild/build/buildd/seed-3.0.0

Tags: ftbfs oneiric
Matthias Klose (doko)
Changed in seed (Ubuntu):
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Matthias Klose (doko) wrote :

Program received signal SIGSEGV, Segmentation fault.
0xf7e1927b in ?? () from /lib/i386-linux-gnu/libc.so.6
(gdb) bt
#0 0xf7e1927b in ?? () from /lib/i386-linux-gnu/libc.so.6
#1 0xf7f172e0 in g_strcmp0 () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2 0xf7e9d5b8 in seed_gobject_define_property_from_function_info (ctx=0xf7fbc19c, info=0x8057e60, object=0xf36702a8,
    instance=1) at seed-engine.c:896
#3 0xf7e9f9df in seed_struct_prototype (ctx=0xf7fbc19c, info=0x8057d20) at seed-structs.c:628
#4 0xf7ea2610 in seed_define_gtype_functions (ctx=0xf7fbc19c) at seed-gtype.c:1036
#5 0xf7ea272e in seed_gtype_init (local_eng=0x8056d58) at seed-gtype.c:1060
#6 0xf7e9e0d7 in seed_init_with_context_and_group (argc=0xffffd710, argv=0xffffd714, context=0xf7fbc19c, group=0xf3abd400)
    at seed-engine.c:1688
#7 0xf7e9e1a6 in seed_init_with_context_group (argc=0xffffd710, argv=0xffffd714, group=0xf3abd400) at seed-engine.c:1723
#8 0xf7e9e213 in seed_init (argc=0xffffd710, argv=0xffffd714) at seed-engine.c:1746
#9 0x08048b31 in main (argc=1, argv=0xffffd7a4) at main.c:152
(gdb) up
#1 0xf7f172e0 in g_strcmp0 () from /lib/i386-linux-gnu/libglib-2.0.so.0
(gdb) up
#2 0xf7e9d5b8 in seed_gobject_define_property_from_function_info (ctx=0xf7fbc19c, info=0x8057e60, object=0xf36702a8,
    instance=1) at seed-engine.c:896
896 if (!g_strcmp0 (name, "new"))
(gdb) p name
$1 = (const gchar *) 0x5365c000 <Address 0x5365c000 out of bounds>

Revision history for this message
Matthias Klose (doko) wrote :
Revision history for this message
Matthias Klose (doko) wrote :

configure does ignore setting of CFLAGS

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

should be fixed with 3.2.0 in the unapproved queue

Changed in seed (Ubuntu Oneiric):
status: Confirmed → Fix Committed
Changed in seed (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.

Other bug subscribers

Remote bug watches

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