From owner-freebsd-hackers Sun Dec 8 13:41:11 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA24947 for hackers-outgoing; Sun, 8 Dec 1996 13:41:11 -0800 (PST) Received: from hamby1.lightside.net (hamby1.lightside.net [207.67.176.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA24941 for ; Sun, 8 Dec 1996 13:41:07 -0800 (PST) Received: from localhost (jehamby@localhost) by hamby1.lightside.net (8.8.3/8.8.2) with SMTP id NAA00452 for ; Sun, 8 Dec 1996 13:41:14 -0800 (PST) X-Authentication-Warning: hamby1.lightside.net: jehamby owned process doing -bs Date: Sun, 8 Dec 1996 13:41:13 -0800 (PST) From: Jake Hamby X-Sender: jehamby@hamby1 To: hackers@freebsd.org Subject: How do I diagnose user-mode PPP coredumps? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I use the user-mode PPP daemon extensively on my FreeBSD-current box, and often, after a number of HDLC errors, it will coredump. The ppp.log looks like: 12-08 13:30:21 [143] HDLC errors -> FCS: 5 ADDR: 0 COMD: 0 PROTO: 0 12-08 13:31:21 [143] HDLC errors -> FCS: 1 ADDR: 0 COMD: 0 PROTO: 0 12-08 13:32:21 [143] HDLC errors -> FCS: 4 ADDR: 0 COMD: 0 PROTO: 0 12-08 13:33:21 [143] HDLC errors -> FCS: 1 ADDR: 0 COMD: 0 PROTO: 0 12-08 13:35:21 [143] HDLC errors -> FCS: 1 ADDR: 0 COMD: 0 PROTO: 0 12-08 13:36:21 [143] HDLC errors -> FCS: 1 ADDR: 0 COMD: 0 PROTO: 0 12-08 13:36:21 [143] Signal 11, core dump. The weird thing is that process 143 is still alive, and I must manually "kill -9" it, in order for the phone line to hang up. The other problem is that I don't get a core file anywhere, because it seems to be trapping the SIGSEGV. Does anyone else have this problem? What steps should I follow to start tracing it? I don't know why I'm getting the HDLC errors in the first place, but I have seen CRC errors using PPP with other OS's, so it's possible there's a dirty connection on my ISP's end, or on mine. Any help will be greatly appreciated, and I will post a send-pr when I've found the culprit. -- Jake