On Mon, Dec 19, 2005 at 10:48:31PM -0500, Ivan Nestlerode <[EMAIL PROTECTED]> was heard to say: > The scenario required to reproduce the crash is even simpler now. > I have a handful of packages on hold (mozilla-firefox and all of the > e2fsprogs binary packages) and I am trying to purge bittorrent and > libwine-arts. Nothing is being upgraded, downgraded, or installed. I > still get a segfault. > > The backtrace is hard to paste here because gdb's terminal gets totally > messed up when running aptitude inside of it. I assume you can > reproduce it. > > It involves pkgSimulate::Policy::~Policy() which is mentioned in another > Bug (343488). However, applying the patch from that bug did not solve > the problem. Also, downgrading aptitude to version 0.4.0-5 did not solve > the problem either.
Unfortunately, backtraces are generally useless unless you compile the program yourself with -O0 -fno-inline. What exactly do you do to trigger the segfault? Nothing happens when I put all the stuff that's being upgraded on hold and then purge those packages, even if I type 'g'. Daniel
signature.asc
Description: Digital signature
