Bug#133631: marked as done (bugs.debian.org: Segsfault in libapt-pkg-libc6.2-3-2.so.3.2)
Your message dated Sat, 16 Feb 2002 17:00:38 -0700 (MST)
with message-id <[🔎] Pine.LNX.3.96.1020216170002.11534C-100000@wakko.debian.net>
and subject line Bug#133631: A normal user can use libapt
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 12 Feb 2002 22:28:44 +0000
>From colario@softhome.net Tue Feb 12 16:28:44 2002
Return-path: <colario@softhome.net>
Received: from 217-127-11-76.uc.nombres.ttd.es (setepo) [217.127.11.76]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 16alPn-0001QD-00; Tue, 12 Feb 2002 16:28:43 -0600
Received: from setepo by setepo with local (Exim 3.34 #1 (Debian))
id 16alSG-0000ns-00; Tue, 12 Feb 2002 22:31:16 +0000
From: Ayose Cazorla <colario@softhome.net>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: bugs.debian.org: Segsfault in libapt-pkg-libc6.2-3-2.so.3.2
X-Reportbug-Version: 1.99.2
X-Mailer: reportbug 1.99.2
Date: Tue, 12 Feb 2002 22:31:15 +0000
Message-Id: <E16alSG-0000ns-00@setepo>
Sender: setepo <setepo@Ayose>
X-BadReturnPath: setepo@Ayose rewritten as colario@softhome.net
using "From" header
Delivered-To: submit@bugs.debian.org
Package: bugs.debian.org
Version: N/A; reported 2002-02-12
Severity: normal
I try to use apt-get, apt-cache or anything which use libapt.
I debugged it, and I saw this:
(gdb) run dump
Starting program: /tmp/apt-0.5.4/bin/apt-cache dump
Program received signal SIGSEGV, Segmentation fault.
0x400b94d2 in debPackagesIndex::FindInCache (this=0x8059e88, Cache=@0xbffff53c)
at /usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/std/straits.h:125
125 { return strlen (s); }
(gdb) bt
#0 0x400b94d2 in debPackagesIndex::FindInCache (this=0x8059e88, Cache=@0xbffff53c)
at /usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/std/straits.h:125
#1 0x400924f9 in CheckValidity (CacheFile=0xbffff780, Start=0x8058380, End=0x8058388, OutMap=0xbffff7e4)
at pkgcachegen.cc:517
#2 0x4009376c in pkgMakeStatusCache (List=@0x8059e48, Progress=@0xbffff7e8, OutMap=0xbffff7e4,
AllowMem=true) at pkgcachegen.cc:625
#3 0x08052ee9 in main (argc=2, argv=0xbffffa14) at apt-cache.cc:1378
#4 0x4018e6cf in __libc_start_main () from /lib/libc.so.6
(gdb) list
120 static bool is_del(char_type a) { return isspace(a); }
121
122 static int compare (const char_type* s1, const char_type* s2, size_t n)
123 { return memcmp (s1, s2, n); }
124 static size_t length (const char_type* s)
125 { return strlen (s); }
126 static char_type* copy (char_type* s1, const char_type* s2, size_t n)
127 { return (char_type*) memcpy (s1, s2, n); }
128 static char_type* move (char_type* s1, const char_type* s2, size_t n)
129 { return (char_type*) memmove (s1, s2, n); }
(gdb) list pkgcachegen.cc:517
512 (*Start)->Describe().c_str());
513 continue;
514 }
515
516 // FindInCache is also expected to do an IMS check.
517 pkgCache::PkgFileIterator File = (*Start)->FindInCache(Cache);
518 if (File.end() == true)
519 return false;
520
521 Visited[File->ID] = true;
(gdb) list pkgcachegen.cc:625
620 return _error->Error(_("Unable to write to %s"),flNotFile(CacheFile).c_str());
621
622 Progress.OverallProgress(0,1,1,_("Reading Package Lists"));
623
624 // Cache is OK, Fin.
625 if (CheckValidity(CacheFile,Files.begin(),Files.end(),OutMap) == true)
626 {
627 Progress.OverallProgress(1,1,1,_("Reading Package Lists"));
628 return true;
629 }
(gdb)
The error occurs evertyme I run apt-*, so I'm sure that there is a
problem in my libapt.
My sources.list is hear:
#deb http://mnm.uib.es/~gallir/debian dists/sid/
deb ftp://ftp.de.debian.org/debian/ sid main contrib non-free
deb-src ftp://ftp.de.debian.org/debian/ sid main
deb http://non-us.debian.org/debian-non-US sid/non-US main
#deb-src http://non-us.debian.org/debian-non-US sid/non-US main
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux setepo 2.4.18-pre9-xfs-lowlatency #2 vie feb 8 23:16:32 GMT 2002 i686
Locale: LANG=es_ES@euro, LC_CTYPE=es_ES@euro
---------------------------------------
Received: (at 133631-done) by bugs.debian.org; 17 Feb 2002 00:00:40 +0000
>From jgg@debian.org Sat Feb 16 18:00:40 2002
Return-path: <jgg@debian.org>
Received: from cast-ext.ab.videon.ca [206.75.216.34]
by master.debian.org with smtp (Exim 3.12 1 (Debian))
id 16cEky-0000IS-00; Sat, 16 Feb 2002 18:00:40 -0600
Received: (qmail 4582 invoked from network); 17 Feb 2002 00:00:39 -0000
Received: from unknown (HELO wakko.debian.net) ([24.86.210.128]) (envelope-sender <jgg@debian.org>)
by cast-ext.ab.videon.ca (qmail-ldap-1.03) with SMTP
for <colario@softhome.net>; 17 Feb 2002 00:00:39 -0000
Received: from localhost
([127.0.0.1] helo=wakko.debian.net ident=jgg)
by wakko.debian.net with smtp (Exim 3.16 #1 (Debian))
id 16cEkw-0003d8-00; Sat, 16 Feb 2002 17:00:38 -0700
Date: Sat, 16 Feb 2002 17:00:38 -0700 (MST)
From: Jason Gunthorpe <jgg@debian.org>
X-Sender: jgg@wakko.debian.net
To: Ayose <colario@softhome.net>
cc: 133631-done@bugs.debian.org, debian-bugs-dist@lists.debian.org,
APT Development Team <deity@lists.debian.org>, apt@packages.qa.debian.org
Subject: Re: Bug#133631: A normal user can use libapt
In-Reply-To: <[🔎] 1013902152.8008.22.camel@setepo>
Message-ID: <[🔎] Pine.LNX.3.96.1020216170002.11534C-100000@wakko.debian.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Delivered-To: 133631-done@bugs.debian.org
On 16 Feb 2002, Ayose wrote:
> How? I saw that the error was produced in msync(2), so I went to the
> source and add "return true" at the begin of MMap::Sync() and
> MMap::Sync(unsigned long Start,unsigned long Stop). Now, msync(2) is
> disabled, because its code is never executed; however, apt-* works as
> well as before :-)
Well, msync is not supposed to fail. Your system is broken. Are you using
some weird filesystem/linux version?
Jason
Reply to: