From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC 00/17] Merge event loop implementations
Date: Fri, 27 Sep 2019 14:05:00 -0000 [thread overview]
Message-ID: <362e3e88-6e13-598c-6167-91076a6c478e@redhat.com> (raw)
In-Reply-To: <52b71425-e839-99fa-5045-8aaa02eafaef@redhat.com>
On 9/27/19 2:53 PM, Pedro Alves wrote:
> On 9/27/19 12:09 AM, Tom Tromey wrote:
>>>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
>>
>> I'll reply to the rest later, after I absorb it.
>>
>>>> Given that, I removed gdb_fildes_t in this series. However, perhaps
>>>> it is still needed and this series needs some more work. I could use
>>>> some advice here -- when is this code actually needed and is there a
>>>> way I can reproduce any problems? I don't have a Windows host, so I'm
>>>> hoping for some sort of compile-time error using a mingw cross.
>>
>> Pedro> This was already discussed. Do I understand correctly that you're
>> Pedro> going to try to replace gdb_select with gnulib's select?
>>
>> Well, that was an idea, but at Cauldron you pointed out that I could
>> test the event loop under Wine. Also, this week I finally got a gdb
>> build working on Windows, so I may just try that instead. My thinking
>> for both of these is that if the code seems to work ok, then there's no
>> reason to attempt the gnulib thing.
>
> Ah, OK. Using the gnulib select would make gdbserver's stdio mode
> usable on Windows too, but that's certainly not something required
> for this patch series. Can always be done at some other time.
>
> What's the plan for gdb_fildes_t then?
FYI, the patch that introduced gdb_fildes_t came from here:
https://sourceware.org/ml/gdb-patches/2010-08/msg00459.html
Here MSDN talks about Unix vs Windows SOCKET types:
https://docs.microsoft.com/en-us/windows/win32/winsock/socket-data-type-2
But, given that gdb (unlike gdbserver), has been using "int"
for sockets on Windows for a long while, and 64-bit Windows
has been a thing for a long while too, I wonder whether in
practice Windows just makes sure that SOCKET handles
fit in 32-bit integers, exactly to avoid porting headaches...
Given that GDB has been using int, I guess that indeed, we
could most probably ignore this issue and get rid of gdb_fildes_t.
I'm not 100% sure of that, but the evidence suggests it.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2019-09-27 14:05 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 16:51 Tom Tromey
2019-02-24 16:52 ` [RFC 01/17] Remove include from event-loop.c Tom Tromey
2019-02-24 16:52 ` [RFC 11/17] Implement event-loop glue for gdbserver Tom Tromey
2019-02-24 16:52 ` [RFC 16/17] Remove gdb_fildes_t Tom Tromey
2019-02-24 16:52 ` [RFC 12/17] Add the ability to stop the event loop Tom Tromey
2019-02-24 16:52 ` [RFC 02/17] Move gdb-specific code out of start_event_loop Tom Tromey
2019-09-26 14:02 ` Pedro Alves
2019-02-24 16:52 ` [RFC 08/17] Introduce and use flush_streams Tom Tromey
2019-02-24 16:52 ` [RFC 03/17] Move event-loop configury to common.m4 Tom Tromey
2019-02-24 16:52 ` [RFC 15/17] Move gdb_notifier comment Tom Tromey
2019-09-26 14:06 ` Pedro Alves
2019-02-24 16:52 ` [RFC 07/17] Use warning in event-loop Tom Tromey
2019-09-26 14:02 ` Pedro Alves
2019-02-24 16:52 ` [RFC 13/17] Switch gdbserver to common event loop Tom Tromey
2019-02-24 16:52 ` [RFC 17/17] Simplify gdbserver's serial event handling Tom Tromey
2019-09-26 17:36 ` Pedro Alves
2019-10-04 22:08 ` Tom Tromey
2019-02-24 16:52 ` [RFC 10/17] Move event-loop.[ch] to common/ Tom Tromey
2019-09-26 14:06 ` Pedro Alves
2019-10-04 22:06 ` Tom Tromey
2019-02-24 16:52 ` [RFC 14/17] Remove some dead code from event-loop.c Tom Tromey
2019-02-24 16:52 ` [RFC 06/17] Include <chrono> in event-loop.c Tom Tromey
2019-09-26 14:02 ` Pedro Alves
2019-02-24 16:52 ` [RFC 09/17] Introduce async-event.[ch] Tom Tromey
2019-09-26 14:06 ` Pedro Alves
2019-10-04 22:17 ` Tom Tromey
2019-02-24 16:52 ` [RFC 05/17] Remove gdb_usleep.c Tom Tromey
2019-09-26 14:02 ` Pedro Alves
2019-09-26 14:43 ` Tom Tromey
2019-02-24 16:52 ` [RFC 04/17] Move gdb_select.h to common/ Tom Tromey
2019-02-24 17:14 ` [RFC 00/17] Merge event loop implementations Eli Zaretskii
2019-02-24 17:26 ` Tom Tromey
2019-02-24 17:45 ` Eli Zaretskii
2019-02-25 19:57 ` Tom Tromey
2019-02-25 20:30 ` Eli Zaretskii
2019-02-25 20:55 ` Tom Tromey
2019-02-26 16:04 ` Eli Zaretskii
2019-02-26 16:23 ` Tom Tromey
2019-02-26 16:46 ` Eli Zaretskii
2019-09-26 17:47 ` Pedro Alves
2019-09-26 23:09 ` Tom Tromey
2019-09-27 13:53 ` Pedro Alves
2019-09-27 14:05 ` Pedro Alves [this message]
2019-09-27 14:21 ` Eli Zaretskii
2019-09-27 14:53 ` Pedro Alves
2019-09-27 15:32 ` Eli Zaretskii
2019-09-27 19:10 ` Tom Tromey
2020-02-14 2:22 ` Tom Tromey
2020-02-14 17:58 ` Pedro Alves
2020-02-14 18:36 ` Tom Tromey
2019-10-04 22:25 ` Tom Tromey
2020-02-14 18:20 ` Pedro Alves
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=362e3e88-6e13-598c-6167-91076a6c478e@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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