Re: dpkg segfaults

[Adam Stewart Edgar <adam.edgar@ua.edu>]

On Fri, 2002-10-18 at 23:42, Adam Heath wrote:
> On 18 Oct 2002, Adam Stewart Edgar wrote:
> 
> > Ok at this point I have realized that dpkg dies when reading
> > /var/lib/dpkg/info/python2.2-optik.list.  Oddly enough whenever I try to
> > read that file I get a segfault.  Even touch will segfault.  That
> > perplexes me quite a bit.  This seems to be either a kernel problem or a
> > filesystem problem.  Next I will check the file system (fsck) and if
> > thats not it, I will be at a loss.  Has anyone seen anything like this?
> 
> Yeah, if other programs can't read that file, then it can't be dpkg's fault.
> 
> Anything in dmesg?
> 
Process touch (pid: 25293, stackpage=ef189000)
Stack: c0130061 d3ca82c0 e3236940 000001b6 e33c3000 00008941 bffff9fc
c012ff72 
       c89a0dc0 c19ae340 00008941 00000003 e33c3000 00000000 c89a0dc0
c19ae340 
       e33c3013 00000014 ded9c84b 00000010 00000000 c01302b6 e33c3000
00008941 
Call Trace:    [<c0130061>] [<c012ff72>] [<c01302b6>] [<c0106cef>]

Code: 69 6f 6e 00 6d 65 6d 69 6e 66 6f 00 75 70 74 69 6d 65 00 6c 

Im not a kernel hacker, so I cannot make any sense of this. Who should I
send it to?

Adam S Edgar