Re: dpkg segfaults
On Sat, 2002-10-19 at 10:33, Federico Sevilla III wrote:
> On Sat, Oct 19, 2002 at 10:03:49AM -0500, Adam Stewart Edgar wrote:
> > 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?
>
> AFAIK you pass this through ksymoops on the same machine (so that it has
> a valid System.map to refer to) and send the output of that to the LKML
> with as much details about your kernel and filesystem as possible.
ksymoops is not installed on my box and I cannot install it because dpkg
can not execute because of the segfault. Any other suggestions?
Adam S Edgar
Reply to: