diff options
| author | Andrew Burgess <andrew.burgess@embecosm.com> | 2020-05-05 15:48:13 +0100 |
|---|---|---|
| committer | Andrew Burgess <andrew.burgess@embecosm.com> | 2020-05-07 11:39:39 +0100 |
| commit | d11a9fabab657e592df9167535bc46804937cf18 (patch) | |
| tree | f04a44ab029429caf6b01af8799c41bb6f16ae0d /gdb | |
| parent | ff84cef42fcf80253c47783d37969c9365acfd7f (diff) | |
| download | gdb-d11a9fabab657e592df9167535bc46804937cf18.zip gdb-d11a9fabab657e592df9167535bc46804937cf18.tar.gz gdb-d11a9fabab657e592df9167535bc46804937cf18.tar.bz2 | |
objcopy: Mention 'entry address' in description
The ELF header contains a start address, which is also sometimes
called the entry address. The 'objdump -x' output calls this field
the 'start address', while readelf calls it 'entry point address'.
The linker talks about setting the 'entry' point in its manual.
I've always thought of this field as the 'entry address', and so when
I recently wanted to know if objcopy could adjust this field I opened
up the manual and searched for 'entry', which found no hits.
I thought it would be useful (for people like me) if the description
of 'set-start' and 'adjust-start' in the objcopy manual mentioned the
word 'entry' to make it easier to find.
binutils/ChangeLog:
* doc/binutils.texi: Mention 'entry address' in the set-start and
adjust-start options descriptions.
Diffstat (limited to 'gdb')
0 files changed, 0 insertions, 0 deletions