Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: LRN <lrn1986@gmail.com>
To: gdb-patches@sourceware.org
Subject: Re: [Bug win32/14529] Make gdb capable of JIT-debugging on W32
Date: Tue, 11 Sep 2012 18:31:00 -0000	[thread overview]
Message-ID: <504F835E.2000100@gmail.com> (raw)
In-Reply-To: <504F8297.5090507@redhat.com>

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

On 11.09.2012 22:27, Pedro Alves wrote:
> On 09/11/2012 07:23 PM, LRN wrote: On 11.09.2012 22:08, Pedro Alves
> wrote:
>>>> On 08/31/2012 04:37 PM, LRN wrote:
>>>>>>>>> @@ -1055,6 +1065,7 @@ Options:\n\n\ --dbx DBX
>>>>>>>>> compatibility mode.\n\ --directory=DIR    Search
>>>>>>>>> for source files in DIR.\n\ --epoch
>>>>>>>>> Output information used by epoch emacs-GDB
>>>>>>>>> interface.\n\ + --event=EVENT      Signal the EVENT
>>>>>>>>> when attached to a process. W32 only.\n\
>>>>>>> 
>>>>>>> And also this part.
>>>>> They were, initially. However, gdb contribution
>>>>> documentation said that gdb devs frown upon extra #ifdefs
>>>>> in files that are not platform-specific. The code is mostly
>>>>> platform independent, it's the two W32API functions that
>>>>> only work on W32 (and you can write non-W32 equivalent, if
>>>>> you figure out how to make it work). Thus, i removed extra
>>>>> #ifdefs in main.c and other files.
>>>> 
>>>> Please consider also cross builds.  IOW, a gdb hosted on
>>>> Windows, but that is built to target something else.  In that
>>>> case, as is, you will end up with the option compiled in.
>>>> But if you remove any mention that this is for Windows only,
>>>> it'll be confusing.
> OK, that means moving configure.ac patches from $host_os case 
> to...where? Should i just make a new case "${target}" in 
> *cygwin*|*mingw*) default_w32_jitdbg=1 ;; esac somewhere? Is it
> ${target}, or ${target_os}? What if there are multiple targets
> (i've seen something like that in configure.ac)?
> 
>> Right, that's the issue -- you can't just check the target,
>> because there might be more than one.  So the option should be
>> clear at what it does, and where it applies.
How do i make it clear? By renaming it? Removing the code that enables
it by default?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQEcBAEBAgAGBQJQT4NcAAoJEOs4Jb6SI2CwC1AH/2BGTYrXSwl0F6Ij3sRSzu5a
M5I4jMHIYc+EaUdTibTNQP4Pw2yXSmOAf0ass3ZL8VNrvyl/Gz4mXRk8EvSoEI11
tT6MwUNcrHk2TBuz7h/yl1HN/fvp9sm5p1ahgwV8WCyladtk8X61AmhOrxLA/wha
+JlWbM+VLL6Wk4ZTpEBPSlUEIL2kxQFP7yGZ1O2QKRZ/EDcKcpXnMhpQNrBOMEfz
/oAmF94iyn+KdqEy5oDNVN8c87jBlUMxi0U970FxIBIuEmx6UJekcPWf37Ada1Ba
HxOmxQvGSF5sBvgyCMWUWsqg5pxtHLLp/8s/PQAlP/iDTeWxeoiXVz+Sqa/d4Nc=
=2r+9
-----END PGP SIGNATURE-----


  reply	other threads:[~2012-09-11 18:31 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
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 [this message]
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=504F835E.2000100@gmail.com \
    --to=lrn1986@gmail.com \
    --cc=gdb-patches@sourceware.org \
    /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