Date: Wed, 6 Nov 2024 16:09:38 -0800 From: Mark Millard <marklmi@yahoo.com> To: "tuexen@freebsd.org" <tuexen@FreeBSD.org> Cc: Bakul Shah <bakul@iitbombay.org>, FreeBSD ARM List <freebsd-arm@freebsd.org> Subject: Re: kernel core debugging Message-ID: <290F4D59-328A-463C-85F0-8E9393D8F84E@yahoo.com> In-Reply-To: <4B430EC2-C328-4FAB-BEBF-CA21D208F78C@freebsd.org> References: <34E3792D-E464-45A8-938A-AD266F2EB49F@freebsd.org> <D4BBF2A8-53FB-482B-AC24-0CD52F36869D@yahoo.com> <92795A92-653D-4DED-ADB2-3BAAF181B813@freebsd.org> <078E5E0E-E90E-48D3-BED0-66C21343DBF5@yahoo.com> <CAEC4664-1271-4101-82FF-417A663AD832@freebsd.org> <FB6DA0D9-6773-4533-A53C-FBF737931D9F@yahoo.com> <F79892F7-73D3-4D25-A915-5D354C705DBA@iitbombay.org> <4B430EC2-C328-4FAB-BEBF-CA21D208F78C@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 6, 2024, at 14:24, tuexen@freebsd.org <tuexen@FreeBSD.org> wrote: >=20 >> On 6. Nov 2024, at 19:27, Bakul Shah <bakul@iitbombay.org> wrote: >>=20 >> My guess: either the core and the kernel don't match or the core is = corrupted. > I'm running a test script resulting in the panic. Doing the same on an > amd64 box results in kgdb being usable to debug the problem. Just want > to use the arm64 box for it... If the panic is readily/simply reproducible on a system without any special builds/installs or specialized hardware, I could try seeing if I get the same kgdb behavior from a locally produced example vmcore.* for it. I'd need instructions on how to cause the panic. =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?290F4D59-328A-463C-85F0-8E9393D8F84E>