From owner-freebsd-current Sun Mar 10 17: 3:35 2002 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 9380737B420; Sun, 10 Mar 2002 17:03:32 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 71E1E7831E; Mon, 11 Mar 2002 11:33:30 +1030 (CST) Date: Mon, 11 Mar 2002 11:33:30 +1030 From: Greg Lehey To: Robert Watson Cc: current@FreeBSD.org Subject: Re: Serial break into debugger broken from 'cu' on -CURRENT? Message-ID: <20020311113330.F36158@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sunday, 10 March 2002 at 10:07:07 -0500, Robert Watson wrote: > > For the past couple of months, I've been working with a set of identical > test boxes from SGI which, for some reason, stopped responding to serial > break on the serial console. I switched to the 'alternative break' option > in LINT, and things work fine. I assumed it was actually some issue with > that particular batch of machines, since no one else had had a problem, > and I didn't really have time to follow up. Yesterday, I brought online > two more crash boxes via serial console, both older TeleNet servers, and > noticed that neither of them respond to serial break over the serial > console using cu. This leads me to wonder two things: > > (1) Is serial break currently broken in -CURRENT Yes, I think so. > (2) Is serial break currently broken in 'cu'? No opinion, since I haven't tried using it. What I have observed is: I use the same gdb for remote serial debugging both for FreeBSD and Linux (ia32). That's right, it's a FreeBSD box running FreeBSD gdb in both cases. I can break to the Linux kernel, but not to the FreeBSD kernel. From this, I conclude that it's a kernel issue, not a gdb issue. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message