From: Stephen Smith <ischis2@home.com>
To: DJ Delorie <dj@redhat.com>
Cc: GDB <gdb@sourceware.cygnus.com>
Subject: Re: GDB for PE/Cywin target won't build on linux
Date: Fri, 13 Jul 2001 15:26:00 -0000 [thread overview]
Message-ID: <3B4F7593.AACCCB5A@home.com> (raw)
In-Reply-To: <200107132206.SAA27799@greed.delorie.com>
Hmm ... I guess that I will learn alot. However, if I compile insight/gdb natively on a
Windows NT/Cygwin box, I have no trouble debugging my embedded machine so maybe
it won't be too bad.
DJ Delorie wrote:
> FYI gdb is one of those things that usually needs to be customized for
> each new type of embedded thingy. The existing cygwin config, for
> example, assumes it's native on a Win32 platform.
next prev parent reply other threads:[~2001-07-13 15:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 15:50 x86-linux -> x86-pe GDB will not configure Stephen Smith
2001-07-13 12:22 ` GDB for PE/Cywin target won't build on linux Stephen Smith
2001-07-13 14:41 ` DJ Delorie
2001-07-13 15:02 ` Stephen Smith
[not found] ` <200107132206.SAA27799@greed.delorie.com>
2001-07-13 15:26 ` Stephen Smith [this message]
2001-07-16 11:49 ` Stephen Smith
2001-07-16 12:33 ` Kevin Buettner
2001-07-16 12:52 ` DJ Delorie
2001-07-16 14:27 ` Stephen Smith
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=3B4F7593.AACCCB5A@home.com \
--to=ischis2@home.com \
--cc=dj@redhat.com \
--cc=gdb@sourceware.cygnus.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