apt-get barfs with a SIGSEGV

[Laurent de Segur <ldesegur@mac.com>]

Hi,

Running Woody latest on ppc. I never had trouble running apt-get but today I
got apt-get to exit with with a SIGSEGV twice in a row. Fortunately, the
second time I was running the bogger with gdb and I caught this:

This GDB was configured as "powerpc-unknown-linux-gnu".
(gdb) file apt-get
Reading symbols from apt-get...(no debugging symbols found)...done.
(gdb) run -b source openmotif
Starting program: /usr/bin/apt-get -b source openmotif
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
Reading Package Lists... Done
Building Dependency Tree... Done
(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
0xff7dc64 in pkgSrcRecords::~pkgSrcRecords ()
  from /usr/lib/libapt-pkg-libc6.2-3-2.so.3.1
(gdb) bt
#0  0xff7dc64 in pkgSrcRecords::~pkgSrcRecords ()
  from /usr/lib/libapt-pkg-libc6.2-3-2.so.3.1
#1  0x1001519c in _init ()
#2  0xff4bebc in CommandLine::DispatchArg ()
  from /usr/lib/libapt-pkg-libc6.2-3-2.so.3.1
#3  0x1001a248 in _init ()
#4  0xfc9a820 in __libc_start_main () from /lib/libc.so.6
#5  0x0 in ?? ()

Is this enough information to track the problem? I still have my gdb session
opened and can dump more if needed.

My apt-get is a vanilla testing release as shown below:

apt 0.5.3 for linux powerpc compiled on Mar  8 2001 20:47:22
Supported Modules:
*Ver: Standard .deb
*Pkg:  Debian dpkg interface (Priority 30)
S.L: 'deb' Standard Debian binary tree
S.L: 'deb-src' Standard Debian source tree
Idx: Debian Source Index
Idx: Debian Package Index
Idx: Debian dpkg status file

Has anyone seen that? Is this a known bug? (I'll have to admit: I am not
very familiar with the debian bug tracking system.)

Thanks for your help,


Laurent