From owner-freebsd-hackers Sat Aug 30 18:11:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA10737 for hackers-outgoing; Sat, 30 Aug 1997 18:11:45 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA10716 for ; Sat, 30 Aug 1997 18:11:38 -0700 (PDT) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id BAA24090; Sun, 31 Aug 1997 01:44:55 +0100 (BST) Message-Id: <199708310044.BAA24090@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: Kenneth Merry cc: brian@awfulhak.org (Brian Somers), mestery@winternet.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Sig 12's with user PPP In-reply-to: Your message of "Fri, 29 Aug 1997 00:44:04 MDT." <199708290644.AAA28380@pluto.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 31 Aug 1997 01:44:54 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Brian Somers wrote... > > > Sounds *really* like an installation thing. Can you remove the UID > > bit on ppp and run it as root. You should get a core with the sig 12 > > - it would be interesting to know what the syscall problem is. > > I'm having trouble with ppp, except I get sig 10's and 11's. I > also get sio overflows all the time... > > sio1: 1 more silo overflow (total 1) > sio1: 1 more silo overflow (total 2) > pid 337 (ppp), uid 0: exited on signal 10 > pid 642 (ppp), uid 0: exited on signal 11 > pid 660 (ppp), uid 0: exited on signal 10 > sio1: 1 more silo overflow (total 3) > sio1: 1 more silo overflow (total 4) > > I compiled ppp with the debugging symbols in, and took the setuid > bit off it. Below is what happened when it crashed...gdb seems to be > unhappy. > > BTW, I'm running a SMP system as well. (the kernel is from August > 13th) > > Ken > -- > Kenneth Merry > ken@plutotech.com > > > # gdb ppp > GDB is free software and you are welcome to distribute copies of it > under certain conditions; type "show copying" to see the conditions. > There is absolutely no warranty for GDB; type "show warranty" for details. > GDB 4.16 (i386-unknown-freebsd), > Copyright 1996 Free Software Foundation, Inc... > (gdb) set args pluto > (gdb) run > Starting program: /usr/sbin/ppp pluto > User Process PPP. Written by Toshiharu OHNO. > Using interface: tun0 > Interactive mode > Dial attempt 1 of 1 > Phone: 1234567 > dial OK! > login OK! > ppp ON > Packet mode. > Warning: No password entry for this host in ppp.secret > Warning: Manipulation is allowed by anyone > ppp ON thunderdome> > PPP ON thunderdome> > Program received signal SIGBUS, Bus error. > 0x183f1 in VjCompInput (bp= > Error accessing memory address 0xefffffa4: Invalid argument. > ) at /usr/src/usr.sbin/ppp/vjcomp.c:143 > 143 } > (gdb) where > #0 0x183f1 in VjCompInput (bp= > Error accessing memory address 0xefffffa4: Invalid argument. > ) at /usr/src/usr.sbin/ppp/vjcomp.c:143 > Error accessing memory address 0xefffff9c: Invalid argument. > I dunno how much I can do with this. Does "disable vjcomp" and "deny vjcomp" make the problem go away ? If so, it looks as if something in the bit that uncompresses a packet is scribbling on the return address. You'll need to delve a bit deeper to try to get more info. I haven't heard of this problem before. -- Brian , Don't _EVER_ lose your sense of humour....