From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>,
Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH] gdb, gdbserver: remove configure check for fs_base/gs_base in user_regs_struct
Date: Mon, 27 Apr 2020 10:48:18 -0400 [thread overview]
Message-ID: <1d103ec9-811e-5705-3b73-db2127eef53b@simark.ca> (raw)
In-Reply-To: <87lfmhq97o.fsf@tromey.com>
On 2020-04-27 10:44 a.m., Tom Tromey wrote:
>>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Simon> I recently stumbled on this code mentioning Linux kernel 2.6.25, and
> Simon> thought it could be time for some spring cleaning (newer GDBs probably
> Simon> don't need to supports 12-year old kernels). I then found that the
> Simon> "legacy" case is probably broken anyway, which gives an even better
> Simon> motivation for its removal.
>
> Thanks for the extensive analysis.
> This seems good to me.
>
> Tom
>
Thanks, I pushed it.
Simon
prev parent reply other threads:[~2020-04-27 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 21:21 Simon Marchi
2020-04-27 14:44 ` Tom Tromey
2020-04-27 14:48 ` Simon Marchi [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=1d103ec9-811e-5705-3b73-db2127eef53b@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.com \
--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