safe_strsignal PARAMS ((int));
extern void
-init_malloc PARAMS ((PTR));
+init_malloc PARAMS ((void *));
extern void
request_quit PARAMS ((int));
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,
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 */
extern int
input_from_terminal_p PARAMS ((void));
-extern int
-catch_errors PARAMS ((int (*) (char *), char *, char *));
-
/* From printcmd.c */
extern void
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
#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
# define NORETURN volatile
# endif
#endif
+#endif /* not 1 */
/* Defaults for system-wide constants (if not defined by xm.h, we fake it). */
extern NORETURN void /* Does not return to the caller. */
nomem PARAMS ((long));
+/* Reasons for calling return_to_top_level. */
+enum return_reason {
+ /* User interrupt. */
+ RETURN_QUIT,
+
+ /* Any other error. */
+ RETURN_ERROR
+};
+
+#define RETURN_MASK_QUIT (1 << (int)RETURN_QUIT)
+#define RETURN_MASK_ERROR (1 << (int)RETURN_ERROR)
+#define RETURN_MASK_ALL (RETURN_MASK_QUIT | RETURN_MASK_ERROR)
+typedef int return_mask;
+
extern NORETURN void /* Does not return to the caller. */
-return_to_top_level PARAMS ((void));
+return_to_top_level PARAMS ((enum return_reason));
+
+extern int catch_errors PARAMS ((int (*) (char *), void *, char *,
+ return_mask));
extern void
warning_setup PARAMS ((void));
#define LITTLE_ENDIAN 1234
#endif
-/* Target-system-dependent parameters for GDB.
-
- The standard thing is to include defs.h. However, files that are
- specific to a particular target can define TM_FILE_OVERRIDE before
- including defs.h, then can include any particular tm-file they desire. */
+/* Target-system-dependent parameters for GDB. */
/* Target machine definition. This will be a symlink to one of the
tm-*.h files, built by the `configure' script. */
-#ifndef TM_FILE_OVERRIDE
#include "tm.h"
-#endif
/* The bit byte-order has to do just with numbering of bits in
debugging symbols and such. Conceptually, it's quite separate
#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. */
}
#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)
projects / deliverable / binutils-gdb.git / blobdiff