| commit | 91c46d4399e42b2b14ae65ae8637061b67adbd82 | |
| author | Rob Norris <rob.norris@klarasystems.com> | |
| Thu, 9 May 2024 23:56:48 +0000 (10 09:56 +1000) | ||
| committer | Brian Behlendorf <behlendorf1@llnl.gov> | |
| Tue, 14 May 2024 16:48:23 +0000 (14 09:48 -0700) | ||
| tree | 9ee011b4e0056db500da170b9ff48fafcb63d32b | treesnapshot (tar.gz zip) |
| parent | 0a543db37111c28085043da89e452ea6b131c019 | commitdiff |
zdb: bring crash handling over from ztest
ztest has a very nice ability to show a backtrace when there's an
unexpected crash. zdb is used often enough on corrupted data and can
blow up too, so nice output is useful there too.
Sponsored-by: Klara, Inc.
Sponsored-by: Wasabi Technology, Inc.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Rob Norris <rob.norris@klarasystems.com>
Closes #16181
ztest has a very nice ability to show a backtrace when there's an
unexpected crash. zdb is used often enough on corrupted data and can
blow up too, so nice output is useful there too.
Sponsored-by: Klara, Inc.
Sponsored-by: Wasabi Technology, Inc.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Rob Norris <rob.norris@klarasystems.com>
Closes #16181
| cmd/zdb/zdb.c | diffblobblamehistory |