The kernel parts were fixed by r354213 and r354214.
I've used old kgdb to test remote debugging through serial only, not for
inspecting crash dumps.
On Fri, Nov 1, 2019 at 4:34 PM John Baldwin wrote:
> On 11/1/19 12:26 PM, luporl wrote:
> > Well, after evaluating remote kernel debugging through
On 11/1/19 12:26 PM, luporl wrote:
> Well, after evaluating remote kernel debugging through serial port, on
> amd64, I've run into several issues while using latest ports gdb/kgdb.
> I don't remember all of them, but were things like step/next not always
> working, connection being lost, and simila
Well, after evaluating remote kernel debugging through serial port, on
amd64, I've run into several issues while using latest ports gdb/kgdb.
I don't remember all of them, but were things like step/next not always
working, connection being lost, and similar things.
OTOH, /usr/libexec/kgdb worked fi
On 11/1/19 4:28 AM, Leandro Lupori wrote:
> Author: luporl
> Date: Fri Nov 1 11:28:43 2019
> New Revision: 354239
> URL: https://svnweb.freebsd.org/changeset/base/354239
>
> Log:
> [PPC64] Fix GDB sigtramp detection
>
> Current implementation of ppcfbsd_pc_in_sigtramp() seems to take only
Author: luporl
Date: Fri Nov 1 11:28:43 2019
New Revision: 354239
URL: https://svnweb.freebsd.org/changeset/base/354239
Log:
[PPC64] Fix GDB sigtramp detection
Current implementation of ppcfbsd_pc_in_sigtramp() seems to take only 32-bit
PowerPC in account, as on 64-bit PowerPC most kerne
