From: Tom Tromey <tromey@redhat.com>
To: Sanjoy Das <sanjoy@playingwithpointers.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4] Adds a new header file, jit-reader.h.in.
Date: Thu, 28 Jul 2011 16:39:00 -0000 [thread overview]
Message-ID: <m3zkjy5rfi.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1311523427-20501-2-git-send-email-sanjoy@playingwithpointers.com> (Sanjoy Das's message of "Sun, 24 Jul 2011 21:33:44 +0530")
>>>>> "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
next prev parent reply other threads:[~2011-07-28 15:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-24 16:00 JIT debug info parser Sanjoy Das
2011-07-24 16:00 ` [PATCH 3/4] Adds documentation Sanjoy Das
2011-07-24 17:51 ` Eli Zaretskii
2011-07-24 16:00 ` [PATCH 1/4] Adds a new header file, jit-reader.h.in Sanjoy Das
2011-07-28 16:39 ` Tom Tromey [this message]
2011-07-24 17:26 ` [PATCH 2/4] Populates jit-reader.h.in Sanjoy Das
2011-07-28 16:40 ` Tom Tromey
2011-07-24 17:41 ` [PATCH 4/4] Adds platform agnostic dynamic loading code Sanjoy Das
2011-07-28 17:33 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3zkjy5rfi.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sanjoy@playingwithpointers.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox