From: Kevin Buettner <kevinb@cygnus.com>
To: Stephen Smith <ischis2@home.com>, DJ Delorie <dj@redhat.com>,
gdb@sourceware.cygnus.com, Kevin Buettner <kevinb@cygnus.com>
Subject: Re: GDB for PE/Cywin target won't build on linux
Date: Mon, 16 Jul 2001 12:33:00 -0000 [thread overview]
Message-ID: <1010716193231.ZM31023@ocotillo.lan> (raw)
In-Reply-To: <3B53374C.98CC3BFB@home.com>
On Jul 16, 11:49am, Stephen Smith wrote:
> Since the embedded target OS is close to windows/cygwin in
> functionality, I choose to try the config/i386/cygwin.mt file.
>
> Therefore, I added the following line to configure.tgt
> i[3456]86-*-pe*) gdb_target=cygwin ;;
I'm not convinced this was the best idea, but it was certainly
worth a try.
> I then did the usual configure/make step and recieved the following
> error sequence. The wierd pard is that the missing symbols are in
> gdb/win32-nat.c which isn't getting compiled. The file is listed in
> the ALLDEPFILES, but isn't listed in TSOBS, COMMON_OBS, or
> ADD_FILES.
It appears to me that you can't build a cross debugger where cygwin
is the target. This is unfortunate, but it appears that the shared
library support requires that you run a native GDB.
> Am I correct in assuming that it needs to be listed somewhere else?
> Is there a gdb way, or should I do what looks good.
I think you should abandon the ``gdb_target=cygwin'' approach. The
shared library support in win32-nat.c will not do what you want for a
cross debugger. I've glanced over the code and it does not look easy
to fix it for your purposes either. This is why it's in win32-nat.c
instead of somewhere else. Ideally though, I think it would be a
good idea for the solib support to be migrated to solib-win32 or somesuch.
That way it could make use of the existing (common) solib machinery,
though it would still not support cross debugging without some
significant rewriting and cooperation from gdbserver.
For your purposes, I think it'd be better to just use ``gdb_target=embed''.
You'll avoid the shared library nightmares that way. If you find that
you need some sort of shared library support, you'll have to implement
it separately. (This'll likely mean creating a new *.mt file, a new
tm-*.h file, and a new solib-*.c file which'll have the shared library
support that you need.)
Kevin
next prev parent reply other threads:[~2001-07-16 12:33 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
2001-07-16 11:49 ` Stephen Smith
2001-07-16 12:33 ` Kevin Buettner [this message]
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=1010716193231.ZM31023@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=dj@redhat.com \
--cc=gdb@sourceware.cygnus.com \
--cc=ischis2@home.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