From: Christopher Faylor <cgf@redhat.com>
To: gdb@sources.redhat.com
Subject: Re: Using gdb with Borland's free compiler?
Date: Wed, 01 Oct 2003 00:07:00 -0000 [thread overview]
Message-ID: <20031001000752.GA6807@redhat.com> (raw)
In-Reply-To: <3F783251.2030009@redhat.com>
On Mon, Sep 29, 2003 at 09:23:29AM -0400, Andrew Cagney wrote:
>>MinGW is not even one of our supported platforms; you would have to
>>to talk to the MiNGW folks about that.
>
>Given the regular MinGW questions, perhaphs it should be?
If wishes were horses...
Someone actually has to do the work. I'll certainly review it but I'm not
going to do it.
So far the basic problem with just using cygwin's gdb seems to be lack
of understanding of MS-DOS paths. It should be doable to fix up gdb to
understand those better in the cygwin port, if that was the only
problem.
The alternative is to fix readline, fix bfd, and make many other
accommodations for a non-UNIX MinGW environment.
As far as Borland is concerned, I would be surprised if it used a
debugging format that gdb knows about so there would be another hurdle
to getting it working. It would be wonderful to have gdb understand
MSVC windows debug format, though.
cgf
next prev parent reply other threads:[~2003-10-01 0:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 23:24 Michael Elizabeth Chastain
2003-09-29 13:26 ` Andrew Cagney
2003-09-30 22:46 ` Chris Johns
2003-10-01 14:49 ` Andrew Cagney
2003-10-02 3:44 ` Chris Johns
2003-10-02 13:44 ` Christopher Faylor
2003-10-02 22:43 ` Chris Johns
2003-10-02 23:12 ` Andrew Cagney
2003-10-03 2:56 ` Chris Johns
2003-10-01 0:07 ` Christopher Faylor [this message]
2003-10-01 5:03 ` Eli Zaretskii
2003-10-01 5:58 ` Joel Brobecker
2003-10-01 13:10 ` Christopher Faylor
-- strict thread matches above, loose matches on Subject: below --
2003-09-28 22:23 Vivi Orunitia
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=20031001000752.GA6807@redhat.com \
--to=cgf@redhat.com \
--cc=gdb@sources.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