This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
Document FUNCTION_START_OFFSET in gdb/doc/gdbint.texinfo
- To: gdb-patches at sourceware dot cygnus dot com
- Subject: Document FUNCTION_START_OFFSET in gdb/doc/gdbint.texinfo
- From: Jim Blandy <jimb at cygnus dot com>
- Date: Wed, 23 Feb 2000 14:45:04 -0500 (EST)
I've committed this.
2000-02-23 Jim Blandy <jimb@redhat.com>
* gdbint.texinfo (FUNCTION_START_OFFSET): Document.
Index: gdb/doc/gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.2
diff -c -r1.2 gdbint.texinfo
*** gdbint.texinfo 2000/02/22 19:22:25 1.2
--- gdbint.texinfo 2000/02/23 19:30:20
***************
*** 1440,1445 ****
--- 1440,1459 ----
@code{FUNCTION_EPILOGUE_SIZE} to expand into the standard size of a
function's epilogue.
+ @item FUNCTION_START_OFFSET
+ An integer, giving the offset in bytes from a function's address (as
+ used in the values of symbols, function pointers, etc.), and the
+ function's first genuine instruction.
+
+ This is zero on almost all machines: the function's address is usually
+ the address of its first instruction. However, on the VAX, for example,
+ each function starts with two bytes containing a bitmask indicating
+ which registers to save upon entry to the function. The VAX @code{call}
+ instructions check this value, and save the appropriate registers
+ automatically. Thus, since the offset from the function's address to
+ its first instruction is two bytes, @code{FUNCTION_START_OFFSET} would
+ be 2 on the VAX.
+
@item GCC_COMPILED_FLAG_SYMBOL
@item GCC2_COMPILED_FLAG_SYMBOL
If defined, these are the names of the symbols that GDB will look for to