Merge GDB 7.5.1

bfd/doc/syms.texi

 @section Symbols
 BFD tries to maintain as much symbol information as it can when
 it moves information from file to file. BFD passes information
 to applications though the @code{asymbol} structure. When the
 application requests the symbol table, BFD reads the table in
 the native form and translates parts of it into the internal
 format. To maintain more than the information passed to
 applications, some targets keep some information ``behind the
 scenes'' in a structure only the particular back end knows
 about. For example, the coff back end keeps the original
@@ skipping 60 matching lines @@
 writing is closed. The application attaches a vector of
 pointers to pointers to symbols to the BFD being written, and
 fills in the symbol count. The close and cleanup code reads
 through the table provided and performs all the necessary
 operations. The BFD output code must always be provided with an
 ``owned'' symbol: one which has come from another BFD, or one
 which has been created using @code{bfd_make_empty_symbol}.  Here is an
 example showing the creation of a symbol table with only one element:
 
 @example
+       #include "sysdep.h"
        #include "bfd.h"
        int main (void)
        @{
          bfd *abfd;
          asymbol *ptrs[2];
          asymbol *new;
 
          abfd = bfd_openw ("foo","a.out-sunos-big");
          bfd_set_format (abfd, bfd_object);
          new = bfd_make_empty_symbol (abfd);
@@ skipping 379 matching lines @@
 @code{bfd_error_no_memory} -
 Not enough memory exists to create private data for @var{osec}.
 @end itemize
 @example
 #define bfd_copy_private_symbol_data(ibfd, isymbol, obfd, osymbol) \
   BFD_SEND (obfd, _bfd_copy_private_symbol_data, \
             (ibfd, isymbol, obfd, osymbol))
 
 @end example