This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Can I strip some debug section and why we need to cross-compile readelf
- From: loody <miloody at gmail dot com>
- To: binutils at sourceware dot org
- Date: Sun, 8 Mar 2009 21:42:29 +0800
- Subject: Can I strip some debug section and why we need to cross-compile readelf
Dear all:
Below are my debug section I got:
[11] .debug_line PROGBITS 00000000 12b044 0561d7 00 0 0 1
[12] .debug_info PROGBITS 00000000 18121b 5214b1 00 0 0 1
[13] .debug_abbrev PROGBITS 00000000 6a26cc 03e940 00 0 0 1
[14] .debug_aranges PROGBITS 00000000 6e1010 002f30 00 0 0 8
[15] .debug_pubnames PROGBITS 00000000 6e3f40 00df01 00 0 0 1
[16] .debug_str PROGBITS 00000000 6f1e41 032caa 01 MS 0 0 1
[17] .debug_frame PROGBITS 00000000 724aec 02289c 00 0 0 4
[18] .debug_loc PROGBITS 00000000 747388 0a4e5f 00 0 0 1
[19] .debug_ranges PROGBITS 00000000 7ec1e7 009048 00 0 0 1
When I try to strip "debug_info" section in my program, I find all
debug sections are striped.
Does that mean it is impossible to strip any debug section, since they
have some connection?
BTW, why we need to cross-compile readelf?
In my opinion, readelf is platform independent, since it is used to
parse ELF format, which is a standard, instead of reading the content
of each section like objdump does.
If my assumption is wrong, please correct me.
appreciate your help,
miloody