* breakpoint.c, breakpoint.h (breakpoint_init_inferior): New function

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

diff --git a/gdb/defs.h b/gdb/defs.h
index 203ffe0a6e26523ddbc1b25d5749e14abf5317f2..35749d0c47a93e6de44e7cb0e0f3f3e7a73efb39 100644 (file)
--- a/gdb/defs.h
+++ b/gdb/defs.h
@@ -163,7 +163,7 @@ extern char *
 safe_strsignal PARAMS ((int));
 
 extern void
-init_malloc PARAMS ((PTR));
+init_malloc PARAMS ((void *));
 
 extern void
 request_quit PARAMS ((int));
@@ -180,7 +180,7 @@ discard_cleanups PARAMS ((struct cleanup *));
 
    Should be, once all calls and called-functions are cleaned up:
 extern struct cleanup *
-make_cleanup PARAMS ((void (*function) (PTR), PTR));
+make_cleanup PARAMS ((void (*function) (void *), void *));
 
    Until then, lint and/or various type-checking compiler options will
    complain about make_cleanup calls.  It'd be wrong to just cast things,
@@ -265,10 +265,12 @@ perror_with_name PARAMS ((char *));
 extern void
 print_sys_errmsg PARAMS ((char *, int));
 
-/* From regex.c */
+/* From regex.c or libc.  BSD 4.4 declares this with the argument type as
+   "const char *" in unistd.h, so we can't declare the argument
+   as "char *".  */
 
 extern char *
-re_comp PARAMS ((char *));
+re_comp PARAMS ((const char *));
 
 /* From symfile.c */
 
@@ -353,9 +355,6 @@ extern char *current_directory;
 extern unsigned input_radix;
 extern unsigned output_radix;
 
-/* Baud rate specified for communication with serial target systems.  */
-extern char *baud_rate;
-
 /* Possibilities for prettyprint parameters to routines which print
    things.  Like enum language, this should be in value.h, but needs
    to be here for the same reason.  FIXME:  If we can eliminate this
@@ -415,6 +414,18 @@ enum val_prettyprint
 #endif /* STDC */
 #endif /* volatile */
 
+#if 1
+#define NORETURN /*nothing*/
+#else /* not 1 */
+/* FIXME: This is bogus.  Having "volatile void" mean a function doesn't
+   return is a gcc extension and should be based on #ifdef __GNUC__.
+   Also, as of Sep 93 I'm told gcc is changing the syntax for ansi
+   reasons (so declaring exit here as "volatile void" and as "void" in
+   a system header loses).  Using the new "__attributes__ ((noreturn));"
+   syntax would lose for old versions of gcc; using
+     typedef void exit_fn_type PARAMS ((int));
+     volatile exit_fn_type exit;
+   would win.  */
 /* Some compilers (many AT&T SVR4 compilers for instance), do not accept
    declarations of functions that never return (exit for instance) as
    "volatile void".  For such compilers "NORETURN" can be defined away
@@ -427,6 +438,7 @@ enum val_prettyprint
 #   define NORETURN volatile
 # endif
 #endif
+#endif /* not 1 */
 
 /* Defaults for system-wide constants (if not defined by xm.h, we fake it).  */
 
@@ -811,7 +823,10 @@ strerror PARAMS ((int));                           /* 4.11.6.2 */
 #endif /* Little endian.  */
 #endif /* BITS_BIG_ENDIAN not defined.  */
 
-/* Swap LEN bytes at BUFFER between target and host byte-order.  */
+/* Swap LEN bytes at BUFFER between target and host byte-order.  This is
+   the wrong way to do byte-swapping because it assumes that you have a way
+   to have a host variable of exactly the right size.
+   extract_* are the right way.  */
 #if TARGET_BYTE_ORDER == HOST_BYTE_ORDER
 #define SWAP_TARGET_AND_HOST(buffer,len)
 #else /* Target and host byte order differ.  */
@@ -829,12 +844,24 @@ strerror PARAMS ((int));                          /* 4.11.6.2 */
   }
 #endif /* Target and host byte order differ.  */
 
+/* In findvar.c.  */
+LONGEST extract_signed_integer PARAMS ((void *, int));
+unsigned LONGEST extract_unsigned_integer PARAMS ((void *, int));
+CORE_ADDR extract_address PARAMS ((void *, int));
+
+void store_signed_integer PARAMS ((void *, int, LONGEST));
+void store_unsigned_integer PARAMS ((void *, int, unsigned LONGEST));
+void store_address PARAMS ((void *, int, CORE_ADDR));
+\f
 /* On some machines there are bits in addresses which are not really
    part of the address, but are used by the kernel, the hardware, etc.
    for special purposes.  ADDR_BITS_REMOVE takes out any such bits
    so we get a "real" address such as one would find in a symbol
    table.  ADDR_BITS_SET sets those bits the way the system wants
-   them.  */
+   them.  This is used only for addresses of instructions, and even then
+   I'm not sure it's used in all contexts.  It exists to deal with there
+   being a few stray bits in the PC which would mislead us, not as some sort
+   of generic thing to handle alignment or segmentation.  */
 #if !defined (ADDR_BITS_REMOVE)
 #define ADDR_BITS_REMOVE(addr) (addr)
 #define ADDR_BITS_SET(addr) (addr)