Page MenuHomeFreeBSD

kdump: nicer printing of kill(2) PID argument
ClosedPublic

Authored by kevans on May 24 2025, 4:14 AM.
Tags
None
Referenced Files
F151255888: D50508.id156509.diff
Tue, Apr 7, 3:49 AM
Unknown Object (File)
Mon, Apr 6, 3:21 PM
Unknown Object (File)
Mon, Apr 6, 3:06 AM
Unknown Object (File)
Sun, Apr 5, 11:50 AM
Unknown Object (File)
Sat, Apr 4, 11:10 AM
Unknown Object (File)
Fri, Apr 3, 2:15 PM
Unknown Object (File)
Thu, Apr 2, 2:48 AM
Unknown Object (File)
Thu, Apr 2, 2:16 AM
Subscribers

Details

Summary

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.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

usr.bin/kdump/kdump.c
1031–1032

What exactly does this assignment do? Do we handle negative PID arguments correctly here?

usr.bin/kdump/kdump.c
1031–1032

Forces the sign extension that I tried to manually hand-roll in wait4 so that it gets interpreted correctly.

This revision is now accepted and ready to land.May 24 2025, 1:48 PM
This revision was automatically updated to reflect the committed changes.