On Mon, Mar 31, 2008 at 12:20:07PM +0200, Bram Senders <[EMAIL PROTECTED]> was heard to say: > To be sure that the patch what fixes it, I de-applied it and make > again... but now aptitude still doesn't segfault! Hmm. It doesn't > segfault anymore either with or without the patch. Maybe it's the build > options? I try a straight debuild -- without your patch, and without > any CXXFLAGS, and install that package, run it... no segfault on > preferences! Install the exact same version (0.4.11-3) from the Debian > archive... and it segfaults on preferences! Now I am very confused.
That's weird and disturbing. Unfortunately, I have no idea how the Debian package for powerpc was built, since it's compiled on an autobuilder. The only thing I can think of is that maybe it was built against an incompatible library: for instance, libsigc++-2.0 could have changed its ABI without upstream bumping the SONAME (easy to do by accident with C++ libraries). If this was the case, though, I'd expect aptitude to segfault all over, not just in the preferences screen. BTW: when you installed your hand-built package, you're sure you were running that and not some other version? i.e., if you ran "make install" to install aptitude systemwide, you'll need to remove it to get it out of $PATH. > -rwxr-xr-x 1 bram bram 2287728 2008-03-31 11:48 aptitude-debuild-nopatch > -rwxr-xr-x 1 bram bram 2807768 2008-03-31 11:48 aptitude-debian-archive > > , and a binary diff reveals that they are very different (that may not > mean much, I don't know, I don't have experience with these things). > aptitude-debuild-nopatch doesn't segfault on preferences, > aptitude-debian-archive does. I have no real idea how to interpret a binary diff, but things like the build date and the exact version of each package in the build toolchain will have at least some impact on how the program is built. Does 0.4.11.1-1 segfault for you? Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
