Bug 249461 - build-id: Created .so files are too large
build-id: Created .so files are too large
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: binutils (Show other bugs)
rawhide
x86_64 Linux
high Severity low
: ---
: ---
Assigned To: Roland McGrath
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-07-24 16:07 EDT by Jan Kratochvil
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version: binutils-2.17.50.0.17-5.x86_64
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-07-24 16:15:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jan Kratochvil 2007-07-24 16:07:56 EDT
Description of problem:
Created -shared files are now at least 2MB (they still work).

Version-Release number of selected component (if applicable):
binutils-2.17.50.0.17-3.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. touch empty.c; gcc -o empty.so empty.c -Wl,-build-id -shared 
2. ls -l empty.so

Actual results:
-rwxrwxr-x 1 jkratoch jkratoch 2102589 2007-07-24 22:06 empty.so*

Expected results:
-rwxrwxr-x 1 jkratoch jkratoch ~5269 2007-07-24 22:06 empty.so*

Additional info:
Section Headers:
[Nr] Name                 Type         Addr             Off      Size     ES
Flags Lk Inf Al
[ 0]                      NULL         0000000000000000 00000000 00000000  0   
    0   0  0
[ 1] .note.gnu.build-id   NOTE         0000000000000000 00200000 00000024  0 A 
    0   0  4

Program Headers:
  Type           Offset   VirtAddr           PhysAddr           FileSiz  MemSiz
  Flg Align
  LOAD           0x200000 0x0000000000000000 0x0000000000000000 0x0004fc
0x0004fc R E 0x200000
  LOAD           0x200500 0x0000000000200500 0x0000000000200500 0x0001e8
0x0001f8 RW  0x200000

I also had problems overcoming this alignment problem before. ;-)

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