From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 0/6] Change gdbserver to use existing gdbsupport
Date: Tue, 10 Mar 2020 18:30:35 -0600 [thread overview]
Message-ID: <87v9nb68d0.fsf@tromey.com> (raw)
In-Reply-To: <20200225222243.8260-1-tom@tromey.com> (Tom Tromey's message of "Tue, 25 Feb 2020 15:22:37 -0700")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> Here's v2 of the patch to change gdbserver to use the existing
Tom> gdbsupport, rather than building its own copy. I've split the patch
Tom> into two parts, as requested, and added some more patches as well --
Tom> since as Pedro pointed out, some builds were broken in the old patch.
Tom> I built this for x86-64, x86, and mingw32. I also confirmed that the
Tom> resulting gdbserver.exe will start up under wine.
I'm planning to check this in soon, so if you have any comments, this
would be a good time.
Tom
prev parent reply other threads:[~2020-03-11 0:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 22:22 Tom Tromey
2020-02-25 22:22 ` [PATCH v2 5/6] Change gdbsupport not to rely on BFD Tom Tromey
2020-02-25 22:22 ` [PATCH v2 6/6] Change gdbserver to use existing gdbsupport Tom Tromey
2020-02-25 22:22 ` [PATCH v2 1/6] Fix CORE_ADDR size assertion in symfile-mem.c Tom Tromey
2020-02-25 22:22 ` [PATCH v2 4/6] Fix gdbserver build when intl already built Tom Tromey
2020-02-25 22:22 ` [PATCH v2 2/6] Don't use sprintf_vma for CORE_ADDR Tom Tromey
2020-02-25 22:22 ` [PATCH v2 3/6] Cast to bfd_vma in arm-tdep.c Tom Tromey
2020-03-11 3:38 ` Simon Marchi
2020-03-12 17:58 ` Tom Tromey
2020-03-12 18:05 ` Simon Marchi
2020-03-12 19:35 ` Tom Tromey
2020-03-11 0:30 ` 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=87v9nb68d0.fsf@tromey.com \
--to=tom@tromey.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