This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 1/4] Adds a new header file, jit-reader.h.in.
>>>>> "Sanjoy" == Sanjoy Das <sanjoy@playingwithpointers.com> writes:
Sanjoy> jit-reader.h.in will host the interface to be implemented and
Sanjoy> the API to be used by the reader. The file needs to be processed
Sanjoy> by ./configure to get the correct typedef for GDB_CORE_ADDR.
Sanjoy> +AC_CHECK_SIZEOF(unsigned long long)
Sanjoy> +AC_CHECK_SIZEOF(unsigned long)
Sanjoy> +AC_CHECK_SIZEOF(unsigned __int128)
Sanjoy> +
Sanjoy> +if test "x${ac_cv_sizeof_unsigned_long}" = "x8"; then
Sanjoy> + HOST_U_64_BIT="unsigned long"
Sanjoy> +elif test "x${ac_cv_sizeof_unsigned_long_long}" = "x8"; then
Sanjoy> + HOST_U_64_BIT="unsigned long long"
Sanjoy> +elif test "x${ac_cv_sizeof_unsigned___int128}" = "x16"; then
Sanjoy> + HOST_U_64_BIT="unsigned __int128"
Sanjoy> +else
Sanjoy> + AC_MSG_ERROR([could not find a 64 bit integer type])
It should not be a fatal error if a 64-bit type cannot be found. It is
possible to build GDB on a 32-bit host that does not have a 64-bit type.
Nothing prevents this; you just won't be able to debug 64-bit processes.
Sanjoy> +# The default path from which to load readers
Sanjoy> +GDB_JIT_READER_PATH="${prefix}/lib/gdb"
It is more normal to use libdir here, but then you get into problems
with how configure represents these variables. There may be some
helpful macros in config/, not sure.
Sanjoy> + extern int __gdb_reader_interface_version (void) \
No need for the leading "__".
Tom