Le samedi 29 mai 2010 à 15:44 +0200, Josselin Mouette a écrit : > > make[5]: Entering directory > > `/build/buildd-seed_2.30.0-1-ia64-em4hmt/seed-2.30.0/doc/modules/readline' > > ../../../src/seed ../../../doc/modules/make-functions.js > > ../../../doc/modules/readline/readline.js > > > ../../../doc/modules/readline/readline-funcs.xml > > > > ** (seed:307): CRITICAL **: Line 0 in (null): (null) (null) > > > > As well as being rc in it's own right this bug is blocking the migration > > of fixes for a number of rc bugs in epiphany-browser.
I have requested the removal of seed/ia64 in unstable so that epiphany can migrate. > After some analysis, it turns out that previous versions of seed can > build but don’t actually work on ia64. > > The bug appeared between 2.27.91-1 and 2.28.0-1, but it turns out it is > not caused by a change in seed. Trying to build seed 2.27.91-1 on a > current ia64 chroot leads to the same failure. So this might actually be > a bug in the toolchain. I’d appreciate now if ia64 porters could have a look. At the time of the g_critical error, the stack is corrupt and I have no idea on how to debug that. I’d appreciate at least some advice on where to look. Program received signal SIGABRT, Aborted. (gdb) bt #0 <signal handler called> Cannot access memory at address 0x28 All I can tell is that it’s not an optimization error since -O0 gives the same result. Thanks, -- .''`. Josselin Mouette : :' : `. `' “If you behave this way because you are blackmailed by someone, `- […] I will see what I can do for you.” -- Jörg Schilling
signature.asc
Description: This is a digitally signed message part
