From: Pedro Alves <palves@redhat.com>
To: LRN <lrn1986@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [Bug win32/14529] Make gdb capable of JIT-debugging on W32
Date: Tue, 11 Sep 2012 18:21:00 -0000 [thread overview]
Message-ID: <504F811C.8000409@redhat.com> (raw)
In-Reply-To: <504D4EE1.5010507@gmail.com>
On 09/10/2012 03:22 AM, LRN wrote:
>
> +# This feature requires 3 things:
> +# 1) windows.h with SetEvent() and CloseHandle() prototypes
> +# 2) inttypes.h with uintptr_t type defined
> +# 3) libkernel32 that exports SetEvent() and CloseHandle()
> +# Because functions in (1) use stdcall on W32, it's impossible to
> +# check them with AC_SEARCH_LIBS.
> +# Until a more elaborate check is written (compile_ifelse or something),
> +# users will have to enable this feature explicitly.
> +# However, this feature is enabled by default for platforms where it should
> +# normally work (MinGW and Cygwin).
> +
> +AC_ARG_ENABLE(w32-jitdbg,
> +AS_HELP_STRING([--enable-w32-jitdbg], [enable W32 JIT debugging]),
> + [case $enableval in
> + yes) w32_jitdbg=1 ;;
> + no) w32_jitdbg=0 ;;
> + *)
> + AC_MSG_ERROR([bad value $enableval for --enable-w32-jitdbg]) ;;
> + esac],
> + [w32_jitdbg=$default_w32_jitdbg])
> +AC_DEFINE_UNQUOTED(W32_JITDBG, $w32_jitdbg,
> + [Define to 1 if W32 JIT debugging support is enabled, to 0 otherwise])
> +
When would you ever want to --enable-w32-jitdbg on anything other than
Windows, where it is enabled by default?
--
Pedro Alves
next prev parent reply other threads:[~2012-09-11 18:21 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 17:55 LRN
2012-08-31 14:53 ` Eli Zaretskii
2012-08-31 15:37 ` Christopher Faylor
2012-08-31 15:40 ` LRN
2012-08-31 15:37 ` LRN
2012-09-10 2:22 ` LRN
2012-09-10 18:15 ` Tom Tromey
2012-09-10 18:32 ` LRN
2012-09-11 18:21 ` Pedro Alves [this message]
2012-09-11 18:27 ` LRN
2012-09-11 18:30 ` Pedro Alves
2012-09-11 18:09 ` Pedro Alves
2012-09-11 18:23 ` LRN
2012-09-11 18:27 ` Pedro Alves
2012-09-11 18:31 ` LRN
2012-09-29 12:42 ` LRN
2012-09-29 13:05 ` Eli Zaretskii
2012-09-29 19:32 ` LRN
2012-09-30 7:51 ` Eli Zaretskii
2012-09-30 12:46 ` LRN
2012-10-01 13:18 ` Eli Zaretskii
2012-10-01 16:22 ` LRN
2012-10-01 22:37 ` Sergio Durigan Junior
2012-10-01 22:48 ` LRN
2012-10-02 5:53 ` Sergio Durigan Junior
2012-10-02 12:48 ` Joel Brobecker
2012-10-02 12:57 ` LRN
2016-06-30 13:17 ` LRN
2016-06-30 15:25 ` Eli Zaretskii
2016-06-30 15:44 ` LRN
2016-06-30 16:23 ` Eli Zaretskii
2016-06-30 17:19 ` LRN
2016-06-30 17:42 ` Eli Zaretskii
2016-06-30 18:36 ` LRN
2016-06-30 18:57 ` Eli Zaretskii
2016-06-30 19:14 ` LRN
2016-07-02 1:16 ` LRN
2016-07-02 7:48 ` Eli Zaretskii
2016-07-10 13:06 ` LRN
2016-07-10 14:55 ` Eli Zaretskii
2016-07-18 10:08 ` LRN
2016-07-19 19:10 ` Eli Zaretskii
2016-07-20 4:43 ` LRN
2016-07-23 8:41 ` Eli Zaretskii
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=504F811C.8000409@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=lrn1986@gmail.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