Re: [Bug win32/14529] Make gdb capable of JIT-debugging on W32

LRN
2012-09-11T18:27:02Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11.09.2012 22:21, Pedro Alves wrote:
> 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?
>
No idea. But i like things to have built-in overrides, in case you
need to do something that the developer have not foresaw. Better than
patching gdb in that case.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQEcBAEBAgAGBQJQT4JeAAoJEOs4Jb6SI2CwWSMH/iqniyrvJUf6AB71PEFNW1NV
EBfz4wJvwny2wsLWqH6p/u2N4maYbUsoxFpEJhtcgslPz5ERJu0nJlebzlWYcLLd
zAY67H0aGvVmYG6rZOKnMeV/AI4qzUwuUlMqoWSXN2OcQF7noUN2Fk4bKgjK4Dor
w58Y+UL6EpmnG97xxyWgzCNrCHYwrvu1f8Lln6yIfHUzqL2hWfiVhtMsFWfB4f7H
9J2dszPKuSfew/2MgbthSu9p3Brt7gLQja2Iva+JtApIa+lQMbpTsaQWb2kRJI4m
j4zVlOWb6axQKtAjif78mrcs1P/E9Df3oNa96YPF7TUmMG4naeUhr3FW9OG+Tls=
=7wgJ
-----END PGP SIGNATURE-----