google / google/autofdo

Disscussion: Does autofdo support .zdebug_{info,line}...

Open
#167 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
619
Forks
127
PR merge metrics
No merged PRs in 30d

Description

My default ELF section looks like:

```
$ readelf -S hello1
...
[13] .zdebug_abbrev PROGBITS 000000000056a000 00136000
0000000000000127 0000000000000000 0 0 1
[14] .zdebug_line PROGBITS 000000000056a127 00136127
000000000001d2f2 0000000000000000 0 0 1
[15] .zdebug_frame PROGBITS 0000000000587419 00153419
0000000000005ac1 0000000000000000 0 0 1
[16] .debug_gdb_s[...] PROGBITS 000000000058ceda 00158eda
000000000000002c 0000000000000000 0 0 1
[17] .zdebug_info PROGBITS 000000000058cf06 00158f06
000000000003621b 0000000000000000 0 0 1
[18] .zdebug_loc PROGBITS 00000000005c3121 0018f121
000000000001c80c 0000000000000000 0 0 1
[19] .zdebug_ranges PROGBITS 00000000005df92d 001ab92d
0000000000009691 0000000000000000 0 0 1
```

Does autofdo support `zlib` format of dwarf? or, how compile source code, could swap `.zdebug_info` to `.debug_info`?

FYI: man dwarfdump

```
If zlib compression was used on the DWARF sections in the object file being read the real section names such as
.zdebug_info etc will be reported by dwarfdump. When dwarfdump says something is at offset 55 of .zdebug_info (or
the like) keep in mind that the offset applies to the uncompressed section (in memory), not the .zdebug_ compressed
section in objectfilename.
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.