Re: apt-get barfs with a SIGSEGV
Hi,
Replying to my own post to provide more info. This problem is reproducible
when I edit my /etc/apt/sources.files and switch from testing to unstable
and vice-and-versa without doing an apt-get update and just directly doing
an apt-get source of some package. So doing the required apt-get update
after editing the file won't show the problem (that's the workaround.)
Now, I just wished that there would be a friendlier way to tell about this
than throwing a SIGSEGV exception, because obviously there is a bogus
dereferenced pointer in one of the destructors in the apt-get lib.
Laurent
> From: Laurent de Segur <ldesegur@mac.com>
> Date: Thu, 20 Sep 2001 10:42:42 -0700
> To: <debian-powerpc@lists.debian.org>
> Subject: apt-get barfs with a SIGSEGV
> Resent-From: debian-powerpc@lists.debian.org
>
> 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
>
>
>
>
>
> --
> To UNSUBSCRIBE, email to debian-powerpc-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
Reply to: