On Wed, Jun 11, 2003 at 12:12:00PM -0400, Colin Walters wrote: > On Wed, 2003-06-11 at 09:32, Michael Schmitz wrote: > > > >> merge 196563 196060 > > > > Bug#196060: [3.3 regression] [arm] python2.2-2.2.3 gets miscompiled > > > > Bug#196563: fontconfig: [m68k] segfault during postinst > > > > Merged 196060 196563. > > > > > > In any event this is entirely bogus. Miscompilation of two unrelated > > > programs on two unrelated architectures is highly unlikely to be the > > > same bug in gcc; please don't try and merge bugs like this. > > > > The fontconfig segfault happens with any of the 2.1.92-2, 2.2.0-2 or > > 2.2.0-5 versions of fontconfig/libfontconfig on kullervo. > > Ok, that would at first glance appear to void my hypothesis; however, > fontconfig uses freetype, and that could have been miscompiled. Can you > try also downgrading that to a pre gcc-3.3 version? > > What I really need is a gdb backtrace with debugging information.
I tried to rebuild fontconfig with debugging (with DEB_BUILD_ options) info but the gdb output was no different than without debugging info :-( Didn't somebody say recently we have a working gdb again? Christian
