From Fedora Project Wiki

(Created page with "{{QA/Test_Case |description=This test case ensures that `dwz` can optimize DWARF debugging information in ELF binaries without corruption. |setup= 1. Install a fresh copy of Fedora. 2. Ensure `dwz` is installed using: `dnf install dwz`. 3. Compile a helloworld C/C++ application with debugging information: `gcc -g -o sample sample.c`. |actions= # Optimize the debugging information with `dwz`: `dwz sample`. # Use a debugging tool, like `gdb`, to debug the `sample` binary....")
 
No edit summary
 
Line 2: Line 2:
|description=This test case ensures that `dwz` can optimize DWARF debugging information in ELF binaries without corruption.
|description=This test case ensures that `dwz` can optimize DWARF debugging information in ELF binaries without corruption.
|setup=
|setup=
1. Install a fresh copy of Fedora.
# Ensure `dwz` is installed using: `dnf install dwz`.
2. Ensure `dwz` is installed using: `dnf install dwz`.
# Compile a helloworld C/C++ application with debugging information: `gcc -g -o sample sample.c`.
3. Compile a helloworld C/C++ application with debugging information: `gcc -g -o sample sample.c`.


|actions=
|actions=
Line 12: Line 11:


|results=
|results=
# Debugging tools should access the symbols and debug the application without any issues, indicating the DWARF sections were not corrupted.
# `dwz` should complete its optimization without errors.
# `dwz` should complete its optimization without errors.
# Debugging tools should access the symbols and debug the application without any issues, indicating the DWARF sections were not corrupted.
`[r00t@fedora ~]$ dwz sample
dwz: sample: DWARF compression not beneficial - old size 340 new size 340`


|optional=
|optional=
1. Run `dwz` on more complex applications or shared libraries.
# Run `dwz` on more complex applications or shared libraries.
2. Monitor for any size reduction in the debugging information.
# Monitor for any size reduction in the debugging information.
3. Check for speed improvements during debugging due to optimized debug info.
# Check for speed improvements during debugging due to optimized debug info.
}}
}}
[[Category:Package_dwz_test_cases]]
[[Category:Package_dwz_test_cases]]
[[Category:Critical_path_test_cases]]
[[Category:Critical_path_test_cases]]

Latest revision as of 09:56, 21 August 2023

Description

This test case ensures that dwz can optimize DWARF debugging information in ELF binaries without corruption.

Setup

  1. Ensure dwz is installed using: dnf install dwz.
  2. Compile a helloworld C/C++ application with debugging information: gcc -g -o sample sample.c.

How to test

  1. Optimize the debugging information with dwz: dwz sample.
  2. Use a debugging tool, like gdb, to debug the sample binary.
  3. Check if debug symbols are accessible and the application is debuggable.

Expected Results

  1. Debugging tools should access the symbols and debug the application without any issues, indicating the DWARF sections were not corrupted.
  2. dwz should complete its optimization without errors.

[r00t@fedora ~]$ dwz sample dwz: sample: DWARF compression not beneficial - old size 340 new size 340

Optional

  1. Run dwz on more complex applications or shared libraries.
  2. Monitor for any size reduction in the debugging information.
  3. Check for speed improvements during debugging due to optimized debug info.
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_dwz&oldid=686826"