Date: Sun, 18 Feb 2018 10:53:16 -0800 From: Thomas Skibo <thomasskibo@yahoo.com> To: Ian Lepore <ian@freebsd.org> Cc: freebsd-arm@freebsd.org Subject: Re: Entering kdb in early boot Message-ID: <19B30B15-83CE-41A4-8830-CF4D44EA6F45@yahoo.com> In-Reply-To: <1518913084.91697.8.camel@freebsd.org> References: <FADD8596-6CFA-4982-A922-3E0B42607DB3@yahoo.com> <1518913084.91697.8.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Feb 17, 2018, at 4:18 PM, Ian Lepore <ian@freebsd.org> wrote: >=20 > On Sat, 2018-02-17 at 15:50 -0800, Thomas Skibo via freebsd-arm wrote: >> Hello: >>=20 >> I noticed that ARM machdep.c doesn=E2=80=99t 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. >>=20 >> While trying to get this to work, I discovered that machdep_boot.c >> doesn=E2=80=99t include opt_ddb.h and so the kernel symbols weren=E2=80= =99t 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. >>=20 >> In any case, I=E2=80=99d be happy to put this up on phabricator if = you like. >>=20 >> =E2=80=94Thomas=20 >>=20 >=20 > Please do. >=20 > -- Ian https://reviews.freebsd.org/D14428 <https://reviews.freebsd.org/D14428>;
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19B30B15-83CE-41A4-8830-CF4D44EA6F45>