Re: What to do (fwd)

D. Chiodo (djc@hal.microwave.com)
Thu, 5 Sep 1996 16:05:07 -0400 (EDT)


I had posted this previously, but no one had any comments/advice/fixes.. I
suspect it was becuase I buried the data at the bottom..

Trace: 120a97 <close_fp+33/84>
Trace: 1150e6 <do_exit+116/1f0>
Trace: 2855e40
Trace: 1151c0 <sys_exit>
Trace: 1151ce <sys_exit+e/10>
Trace: 283f41b
Trace: 2855e40
Trace: 10fae8 <do_page_fault>
Trace: 10a63d <error_code+3d/50>
Trace: 10a429 <lcall7+49/50>

Code: 12c868 <locks_remove_locks+c/38> movl 0x48(%eax),%edx
Code: 12c86b <locks_remove_locks+f/38> testl %edx,%edx
Code: 12c86d <locks_remove_locks+11/38> je 12c891 <locks_remove_locks+35/38>Code: 12c86f <locks_remove_locks+13/38> testb $0x1,0x1c(%edx)
Code: 12c873 <locks_remove_locks+17/38> je 12c884 <locks_remove_locks+28/38>Code: 12c875 <locks_remove_locks+19/38> pushl %ebx
Code: 12c876 <locks_remove_locks+1a/38> addl $0x48,%eax
Code: 12c879 <locks_remove_locks+1d/38> pushl %eax
Code: 12c87a <locks_remove_locks+1e/38> call 9090002c <_EIP+9090002c>
Code: 12c87f <locks_remove_locks+23/38> nop

Ok, it has something to do with locks, which makes me think its libc
again.. I had a devil of a time fixing that the first time, and thought I
had gotten it right with this one.. ldconfig seems to refuse to find
libc-5.3.12..

But as I said originally, I know isnt a kernel problem.. When I chroot to a
drive that used to be my root fs (but has other problems), running the
same kernel, it runs fine..

So its the libraries (or something) on that root fs..

Like I said, I tried copying them over, but still no luck.. (/lib,
/usr/lib, /usr/X11/lib, one at a time, trying to isolate)..

I must seem completely clueless here, and I will admit, I am when it
comes to this sort of debugging.. I appreciate any help you can give me

D. Chiodo
Microwave Systems

On Sat, 24 Aug 1996, Herbert Rosmanith wrote:

> Date: Sat, 24 Aug 1996 19:17:56 +0200 (MET DST)
> From: Herbert Rosmanith <herp@wildsau.idv.uni-linz.ac.at>
> To: "D. Chiodo" <djc@hal.microwave.com>
> Subject: Re: What to do
>
> >
> >
> > Ok, this is probably the wrong place to post, becuase I *know* this is
> > *not* a kernel problem, it has something to do with libraries, or the ibcs
> > module, or some files or config on the root fs. I just have no idea how
> > to find out what it is (I have tried moving shared libraries from a root
> > fs that works, to one that doesnt, with no luck) This usually happens on
> > exit of the program in question, with "Segmentation Fault" being
> > displayed if I ran it from a shell.
> >
> > The processes referenced are COFF binaries.. (WP6 for SCO)
> >
> > I am using kernel 2.0.12, libc 4.7.2, ibcs with a last change date of
> > June 6, 1996, 5k86-p90...
> >
> > Anyway, I would appreciate very much any info on how I can track this
> > down (Its not an intermittent, it happens EVERY time).. I'd even
> > appreciate flames, if they even contain the slightest hint of what to do
> > with this..
> >
> > general protection: 0000
> > CPU: 0
> > EIP: 0010:[<0012c868>]
> > EFLAGS: 00010286
> > eax: f000ef6f ebx: 00e40c0c ecx: 00000000 edx: 00000000
> > esi: f000ef6f edi: 00000001 ebp: 019f3018 esp: 00047f14
> > ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
> > Process wpexc60 (pid: 4238, process nr: 57, stackpage=00047000)
> > Stack: 00000000 00120a97 00e40c0c 00000000 00000001 00000005 001150e6 00000000
> > 00000001 00000001 02855e40 001151c0 001151ce 00000000 0283f41b 00000000
> > 00000000 00000001 00000000 bffffbdc 00213000 002ea000 002ea065 01e06025
> > Call Trace: [<00120a97>] [<001150e6>] [<02855e40>] [<001151c0>]
> > [<001151ce>] [<0283f41b>] [<02855e40>]
> > [<0010fae8>] [<0010a63d>] [<0010a429>]
> > Code: 8b 50 48 85 d2 74 22 f6 42 1c 01 74 0f 53 83 c0 48 50 e8 15
> >
> >
> > general protection: 0000
> > CPU: 0
> > EIP: 0010:[<0012c868>]
> > EFLAGS: 00010286
> > eax: f000ef6f ebx: 01d36018 ecx: 00000000 edx: 00000000
> > esi: f000ef6f edi: 00000001 ebp: 010f9018 esp: 00cf1f14
> > ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
> > Process xwp (pid: 4209, process nr: 79, stackpage=00cf1000)
> > Stack: 00000000 00120a97 01d36018 00000000 00000011 00000005 001150e6 00000000
> > 00000001 009f0001 02855e40 001151c0 001151ce 00000000 0283f41b 00000000
> > 080509c0 009f0868 009f086c bfffe52c 00213000 01d54000 01d54065 0157a025
> > Call Trace: [<00120a97>] [<001150e6>] [<02855e40>] [<001151c0>]
> > [<001151ce>] [<0283f41b>] [<02855e40>]
> > [<0010fae8>] [<0010a63d>] [<0010a429>]
> > Code: 8b 50 48 85 d2 74 22 f6 42 1c 01 74 0f 53 83 c0 48 50 e8 15
> >
>
> read linux/Documentation/BUG-HUNTING.
> run the output above through the programm linux/scripts/ksymoops
>
>