From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Change gdbserver to use existing gdbsupport
Date: Wed, 19 Feb 2020 19:18:00 -0000 [thread overview]
Message-ID: <871rqqwfmf.fsf@tromey.com> (raw)
In-Reply-To: <48984f7d-f851-84c8-1145-95fbfbbade23@redhat.com> (Pedro Alves's message of "Wed, 19 Feb 2020 17:42:05 +0000")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> I'm surprised you didn't hit any problem, because last time we chatted
Pedro> about it, I quickly tried it, and ran into a small number of places
Pedro> that needed adjustment.
Yeah, I'm surprised too.
I just tried a mingw build and it found some issues. So, I will redo it.
Pedro> I'd prefer to see this conversion in two separate patches. One (or more) that
Pedro> removes the bfd dependency from gdb's gdbsupport, which potentially is a material
Pedro> change for making GDB always use 64-bit types, and then a separate change
Pedro> to make gdbserver use top level gdbsupport.
Will do.
Tom
prev parent reply other threads:[~2020-02-19 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 17:06 Tom Tromey
2020-02-19 17:42 ` Pedro Alves
2020-02-19 19:18 ` Tom Tromey [this message]
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=871rqqwfmf.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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