From: Tom Tromey <tromey@redhat.com>
To: Sanjoy Das <sanjoy@playingwithpointers.com>
Cc: gdb-patches@sourceware.org
Subject: Re: JIT Reader
Date: Wed, 02 Nov 2011 17:52:00 -0000 [thread overview]
Message-ID: <m3fwi6xvix.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4EA9095D.5070408@playingwithpointers.com> (Sanjoy Das's message of "Thu, 27 Oct 2011 13:03:49 +0530")
>>>>> "Sanjoy" == Sanjoy Das <sanjoy@playingwithpointers.com> writes:
Sanjoy> This work was stalled for some time while the copyright assignment was
Sanjoy> being worked on; which will be finalized any time now.
Super.
Sanjoy> In the meantime, I've attached a rebased set of patches for final
Sanjoy> reviews.
Thanks, and sorry about the delay. It really is best to ping weekly;
the squeaky wheel etc.
Sanjoy> +#ifdef HAVE_DLFCN_H
Sanjoy> +#include <dlfcn.h>
Sanjoy> +#elif __MINGW32__
Sanjoy> +#include <windows.h>
Sanjoy> +#else
Sanjoy> +/* Unsupported configuration. See Eg. gdb_dlopen for details. */
Sanjoy> +#error API to load shared library missing (Eg. libdl)
Sanjoy> +#endif
I think this should be a runtime error, not a build-time error, because
it seems better to me to make a gdb with reduced functionality than to
prevent the build for just this feature.
Tom
next prev parent reply other threads:[~2011-11-02 17:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 9:41 Sanjoy Das
2011-11-02 17:52 ` Tom Tromey [this message]
2011-11-02 18:04 ` Tom Tromey
2011-11-02 18:30 ` Tom Tromey
2011-11-02 18:38 ` Tom Tromey
2011-11-03 10:38 ` Sanjoy Das
2011-11-03 14:37 ` Tom Tromey
2011-11-03 14:38 ` Tom Tromey
2011-11-03 14:39 ` Tom Tromey
2011-11-03 16:39 ` Sanjoy Das
2011-11-03 17:13 ` Eli Zaretskii
2011-11-03 17:55 ` Sanjoy Das
2011-11-04 2:58 ` Sanjoy Das
2011-11-04 13:49 ` 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=m3fwi6xvix.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