From: Christopher Faylor <cgf-no-personal-reply-needed-please@sourceware.org>
To: gdb@sourceware.org
Subject: Re: Building GDB with MinGW (3)
Date: Sat, 02 Oct 2004 03:37:00 -0000 [thread overview]
Message-ID: <20041002033743.GE14081@trixie.casa.cgf.cx> (raw)
In-Reply-To: <415E1045.7030109@meer.net>
On Fri, Oct 01, 2004 at 07:19:49PM -0700, Dan Mosedale wrote:
>[Third re-send attempt, sorry about the mailer issues]
Who are you apologizing to? If you had problems sending no one would have
seen them.
>Joel Brobecker wrote:
>>>real problem. (READLINE)
>>
>>As far as I can remember, GDB has not been ported to MingW. And indeed,
>>porting readline is one of the problems to solve for that port. There is
>>a group that has posted patches that allow you to build GDB on MingW,
>>they have a web site. I don't know the URL but google should help you
>>find it. Last I heard, they had ported GDB 5.3, but maybe they have
>>patches for a more recent release now.
>
>Actually, it has. See <http://www.mingw.org/download.shtml>.
Maybe at some point someone will actually do it right and try to submit
patches to gdb.
>One of the tarballs for the most recent snapshot version includes the
>patch against the mainline. It's from around May, so I suspect the
>patch will require some massaging if you want it to work against
>current CVS. The best thing about the port is that, unlike the cygwin
>port, hitting ^c to stop the inferior seems to actually work most of
>the time (assuming you run the gdb in a cmd window and not a cygwin
>window). This is because it relies on windows native events rather
>than cygwin signals.
CTRL-C works fine on cygwin. I use it all of the time.
In fact, CTRL-C does not rely on cygwin signals. gdb doesn't know about
cygwin signals from the inferior process. I haven't looked at what
mingw does but it is likely to be the same code.
cgf
next prev parent reply other threads:[~2004-10-02 3:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 14:25 MinGW Cavit Cahit VURAL
2004-10-01 14:36 ` MinGW Fabian Cenedese
2004-10-01 14:51 ` MinGW Cavit Cahit VURAL
2004-10-01 14:56 ` Building GDB with MinGW Cavit Cahit VURAL
2004-10-01 15:10 ` Building GDB with MinGW (2) Cavit Cahit VURAL
2004-10-01 15:16 ` Building GDB with MinGW (3) Cavit Cahit VURAL
2004-10-01 16:51 ` Joel Brobecker
2004-10-02 2:21 ` Dan Mosedale
2004-10-02 3:37 ` Christopher Faylor [this message]
2004-10-02 9:03 ` Building GDB with MinGW (4) Cavit Cahit VURAL
2004-10-02 5:20 ` Cavit Cahit VURAL
2004-10-02 15:14 ` Building GDB with MinGW (3) Dan Mosedale
2004-10-07 12:36 ` Building GDB with MinGW Cavit Cahit VURAL
2004-10-07 12:23 ` Cavit Cahit VURAL
2004-10-07 12:42 ` Cavit Cahit VURAL
2004-10-07 12:48 ` Cavit Cahit VURAL
2004-10-01 20:23 ` Building GDB with MinGW (3) Eli Zaretskii
2004-10-01 21:22 ` Cavit Cahit VURAL
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=20041002033743.GE14081@trixie.casa.cgf.cx \
--to=cgf-no-personal-reply-needed-please@sourceware.org \
--cc=gdb@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