src/usr.bin/kdump, branch main

sys/event.h: use freebsd32_uint64_t for kevent32 64bit members

2026-02-09T18:57:19+00:00

Reviewed by:	brooks
Sponsored by:	The FreeBSD Foundation
MFC after:	1 week
Differential revision:	https://reviews.freebsd.org/D55135

kdump: Add support for decoding inotify events

2025-07-04T14:42:33+00:00

These are emitted when reading from an inotify descriptor.

MFC after:	3 months
Sponsored by:	Klara, Inc.

ktrace: trace and decode thr_new() thr_param

2025-06-04T11:24:20+00:00

Sponsored by:	The FreeBSD Foundation
MFC after:	1 week

kdump: nicer printing of kill(2) PID argument

2025-06-04T01:51:06+00:00

Similar to wait*(), kill(2) operates on a pid that currently gets output
as hex.  Output it in decimal to make it a little easier to eyeball the
pid we're signalling.

Reviewed by:	markj
Differential Revision:	https://reviews.freebsd.org/D50508

kdump: nicer printing of wait*() ID arguments

2025-06-04T01:51:06+00:00

Currently, both of these will print pid/uid/gid/sid/jid in hex, which
isn't very helpful for eyeballing.  Align more closely with truss(1) and
print these in decimal instead.

`ip` is likely wider than our ID type, so we do a small casting trick in
wait4(2) to get it sign-extended and rendered properly.

Reviewed by:	markj
Differential Revision:	https://reviews.freebsd.org/D50496

kdump(1): Use static array for header types string literals

2025-06-03T02:47:38+00:00

Also change sprintf() to snprintf().

Reviewed by:	brooks
Sponsored by:	The FreeBSD Foundation
MFC after:	1 week
Differential revision:	https://reviews.freebsd.org/D50633

kdump: staticise functions in kdump.c

2025-06-03T02:47:38+00:00

Reviewed by:	brooks
Sponsored by:	The FreeBSD Foundation
MFC after:	1 week
Differential revision:	https://reviews.freebsd.org/D50633

kdump(1): pretty-print KTR_EXTERR

2025-06-03T02:47:38+00:00

Reviewed by:	brooks
Sponsored by:	The FreeBSD Foundation
MFC after:	1 week
Differential revision:	https://reviews.freebsd.org/D50633

ktrace: support AF_NETLINK in ktrstruct

2024-11-19T22:19:50+00:00

Right now, sockaddr_nl parameters are not displayed in kdump output,
however they are present in the structure in ktrace.out file when
ktrace is run.

Reviewed by:		melifaro, markj, glebius
Differential Revision:	https://reviews.freebsd.org/D47411

ktrace: log execve(2) arguments and environment

2024-11-11T21:19:35+00:00

Two new events KTR_ARGS and KTR_ENV can be used to
trace arguments of execve(2).

Reviewed by:		glebius
Differential Revision:	https://reviews.freebsd.org/D47127