2011-01-07 Michael Snyder <msnyder@vmware.com>

[deliverable/binutils-gdb.git] / gdb / gdbcore.h

diff --git a/gdb/gdbcore.h b/gdb/gdbcore.h
index cdcb476c373a8160ded7c6aaecc1c9c3af2b4403..04ae18510f71d892d14d1f1e8b1be435d5c9d97b 100644 (file)
--- a/gdb/gdbcore.h
+++ b/gdb/gdbcore.h
@@ -68,13 +68,14 @@ extern ULONGEST read_memory_unsigned_integer (CORE_ADDR memaddr,
                                              int len,
                                              enum bfd_endian byte_order);
 
-/* Read a null-terminated string from the debuggee's memory, given address,
- * a buffer into which to place the string, and the maximum available space */
+/* Read a null-terminated string from the debuggee's memory, given
+   address, a buffer into which to place the string, and the maximum
+   available space.  */
 
 extern void read_memory_string (CORE_ADDR, char *, int);
 
 /* Read the pointer of type TYPE at ADDR, and return the address it
-   represents. */
+   represents.  */
 
 CORE_ADDR read_memory_typed_address (CORE_ADDR addr, struct type *type);
 
@@ -139,7 +140,7 @@ struct core_fns
     /* BFD flavour that a core file handler is prepared to read.  This
        can be used by the handler's core tasting function as a first
        level filter to reject BFD's that don't have the right
-       flavour. */
+       flavour.  */
 
     enum bfd_flavour core_flavour;
 
@@ -148,13 +149,13 @@ struct core_fns
        into the BFD model, or may require other resources to identify
        them, that simply aren't available to BFD (such as symbols from
        another file).  Returns nonzero if the handler recognizes the
-       format, zero otherwise. */
+       format, zero otherwise.  */
 
     int (*check_format) (bfd *);
 
     /* Core file handler function to call to ask if it can handle a
        given core file format or not.  Returns zero if it can't,
-       nonzero otherwise. */
+       nonzero otherwise.  */
 
     int (*core_sniffer) (struct core_fns *, bfd *);
 
@@ -177,7 +178,7 @@ struct core_fns
        REG_ADDR is the offset from u.u_ar0 to the register values relative to
        core_reg_sect.  This is used with old-fashioned core files to locate the
        registers in a large upage-plus-stack ".reg" section.  Original upage
-       address X is at location core_reg_sect+x+reg_addr. */
+       address X is at location core_reg_sect+x+reg_addr.  */
 
     void (*core_read_registers) (struct regcache *regcache,
                                 char *core_reg_sect,