From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Cc: Christopher Faylor <me@cgf.cx>, Mark Mitchell <mark@codesourcery.com>
Subject: Re: PATCH: MinGW readline -- revised
Date: Sun, 24 Jul 2005 21:10:00 -0000 [thread overview]
Message-ID: <20050724211016.GA798@nevyn.them.org> (raw)
In-Reply-To: <200507190011.j6J0B1Ma014410@sethra.codesourcery.com>
On Mon, Jul 18, 2005 at 05:11:01PM -0700, Mark Mitchell wrote:
>
> This patch is the revised GDB-on-MinGW bit.
>
> There are three subparts:
Unfortunately, this is a good example of why unrelated fixes
shouldn't be combined...
> 1) Minor bit-rot in remote-sim.c and ser-tcp.c on MinGW. In
> particular, SIGTRAP is being used unconditionally in the former,
> and the MinGW definition of "close" (in terms of "closesocket")
> needs to be a function-like macro, so as to avoid confusion in
> code like "ops->close = net_close".
I'm not sure why you call this "bit-rot".
The unconditional use of SIGTRAP has been there since the oldest
version of GDB in CVS. Paul posted a patch to provide a default
definition of SIGTRAP instead in two places; his patch is more correct
than yours, and is on the csl-arm branch. See the simulator sources to
understand why you can't just ignore SIGTRAP here; the simulator will
be completely broken by this change. Paul's approach is still somewhat
incorrect, in that there is no valid excuse for using native signal
numbers here. The simulators really need to be fixed, but it would be
a Herculean effort. I am inclined to go with Paul's patch for the
nonce.
Similarly the reference to ops->close is from 2002.
> 2) On the GDB side, I've added a win32-termcap.c file that contains
> the stub termcap implementation. There seemed to be no consensus
> that it belongs in libiberty, so I've submitted it here. I'd
> really appreciate being able to check this in; if it's later
> decided that it's wanted in libiberty, I'll happily move it.
>
> 3) On the readline side, I've backported the MinGW changes that will
> be in readline 5.1.
These look fine; the changes aren't quite the way I'd have liked them,
but if they've been taken for readline 5.1, it's important that we
minimize divergence. Chris, do these parts look OK to you?
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-07-24 21:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 0:11 Mark Mitchell
2005-07-22 7:29 ` Kai Henningsen
2005-07-24 21:10 ` Daniel Jacobowitz [this message]
2005-07-24 22:50 ` Mark Mitchell
2005-07-24 23:00 ` Daniel Jacobowitz
2005-07-24 23:03 ` Mark Mitchell
2005-07-25 0:39 ` Christopher Faylor
2005-07-25 0:41 ` Daniel Jacobowitz
2005-07-25 14:54 ` Christopher Faylor
2005-07-25 14:55 ` Mark Mitchell
2005-07-25 15:01 ` Daniel Jacobowitz
2005-07-25 15:02 ` Mark Mitchell
2005-07-25 15:10 ` Mark Mitchell
2005-07-25 0:41 ` Mark Mitchell
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=20050724211016.GA798@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mark@codesourcery.com \
--cc=me@cgf.cx \
/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