From owner-freebsd-arm@freebsd.org Sun Feb 18 00:18:07 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DEDBCF1FCCB for ; Sun, 18 Feb 2018 00:18:07 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 70941752E1 for ; Sun, 18 Feb 2018 00:18:07 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 1fa9d1c1-1441-11e8-b951-f99fef315fd9 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id 1fa9d1c1-1441-11e8-b951-f99fef315fd9; Sun, 18 Feb 2018 00:17:37 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w1I0I4g1050495; Sat, 17 Feb 2018 17:18:04 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1518913084.91697.8.camel@freebsd.org> Subject: Re: Entering kdb in early boot From: Ian Lepore To: Thomas Skibo , freebsd-arm@freebsd.org Date: Sat, 17 Feb 2018 17:18:04 -0700 In-Reply-To: References: Content-Type: text/plain; charset="windows-1251" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Feb 2018 00:18:08 -0000 On Sat, 2018-02-17 at 15:50 -0800, Thomas Skibo via freebsd-arm wrote: > Hello: > > I noticed that ARM machdep.c doesn’t support entering kdb on boot > (boot -d from the loader).  I looked to see how other architectures > implement it and came up with an easy patch. > > While trying to get this to work, I discovered that machdep_boot.c > doesn’t include opt_ddb.h and so the kernel symbols weren’t getting > loaded into the debugger early in the boot (see the call to > db_fetch_ksymtab() in freebsd_parse_boot_param()).  I have never > noticed any problems with symbols in kdb before.  I wonder how those > symbols eventually get loaded and wonder if now I'm calling it twice. > > In any case, I’d be happy to put this up on phabricator if you like. > > —Thomas  > Please do. -- Ian