Bug 2170283 - Rebase to the latest upstream crash-utility(crash-8)
Summary: Rebase to the latest upstream crash-utility(crash-8)
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: crash
Version: 9.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 9.3
Assignee: lijiang
QA Contact: xiaoying yan
Sujata Kurup
URL:
Whiteboard:
Depends On:
Blocks: 2152897 2156543 2156740 2157038 2160464 2166269 2170851 2173896
TreeView+ depends on / blocked
 
Reported: 2023-02-16 02:34 UTC by lijiang
Modified: 2023-08-07 11:37 UTC (History)
3 users (show)

Fixed In Version: crash-8.0.3-1.el9
Doc Type: Enhancement
Doc Text:
.`crash` has been rebased to version 8.0.3 The `crash` utility has been rebased to version 8.0.3. `crash` is an interactive utility to analyze a running system as well as a core dump file created by `kdump` in the event of a kernel crash. The rebase includes many bug fixes and enhancements. The most notable enhancement is the added IPv6 support. For network interfaces that support IPv6, the `crash` utility prints IPv6 addresses with the `net` or the `net -s` command. The `net` command displays the list of network devices, names, and the IP address. The `net -s` command displays the following information: * The open network socket and sock addresses * The family and the type of sockets and sock addresses * The source and destination address and ports for `INET` and `INET6` families
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-148795 0 None None None 2023-02-16 02:36:51 UTC

Description lijiang 2023-02-16 02:34:34 UTC 
Description of problem:

Rebase to the latest upstream crash-utility(crash-8).

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Note You need to log in before you can comment on or make changes to this bug.