From: Fabrice Gautier <gautier@email.enst.fr>
To: jtc@redback.com
Cc: gdb@sources.redhat.com
Subject: Re: gdbserver build
Date: Tue, 01 May 2001 16:00:00 -0000 [thread overview]
Message-ID: <20010502003955.F26A.GAUTIER@email.enst.fr> (raw)
In-Reply-To: <5mk8404sih.fsf@jtc.redback.com>
On 01 May 2001 15:24:38 -0700
jtc@redback.com (J.T. Conklin) wrote:
> >>>>> "Fabrice" == Fabrice Gautier <gautier@email.enst.fr> writes:
> >>
> >> Have you configure and built a GDB in the same object directory that
> >> you're trying to build gdbserver?
>
> I suspect you need to at least configure.
In fact i did have to build gdb.
> I think gdbserver is at a crossroads. While we could make it not
> depend on other parts GDB, recently (where recently is defined as "in
> the last few years") we've talked about possibilities of GDB and
> gdbserver sharing even more code (like the code that's used to fetch
> and store registers). I'm not sure which direction that will
> eventually be followed.
As i see it, gdbserver shoudl be the only one doing target operations
(fecthing register for example) and the rest of gdb (the inferace part) should
be a separate thing talking to a gdbserver (or a stub).
Today you can use gdbserver to do native debugging and not only remote
debugging... why bother having all the native stuff in gdb itself...?
Well just my 2 cents...
--
Fabrice Gautier <gautier@email.enstfr>
prev parent reply other threads:[~2001-05-01 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-01 14:45 Fabrice Gautier
2001-05-01 14:50 ` J.T. Conklin
2001-05-01 15:04 ` Fabrice Gautier
2001-05-01 15:24 ` J.T. Conklin
2001-05-01 16:00 ` Fabrice Gautier [this message]
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=20010502003955.F26A.GAUTIER@email.enst.fr \
--to=gautier@email.enst.fr \
--cc=gdb@sources.redhat.com \
--cc=jtc@redback.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