From: Yue Lu <hacklu.newborn@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Thomas Schwinge <thomas@codesourcery.com>,
gdb-patches <gdb-patches@sourceware.org>,
Luis Machado <lgustavo@codesourcery.com>,
bug-hurd@gnu.org
Subject: Re: [PATCH 1/2] Port gdbserver to GNU/Hurd
Date: Mon, 09 Sep 2013 10:21:00 -0000 [thread overview]
Message-ID: <CAB8fV=hwB_E=5q7o+1AfnJnLiCuG0h_mTy=t8dAttR1+CJ+SmQ@mail.gmail.com> (raw)
In-Reply-To: <5228DBA7.9050408@redhat.com>
Hi,
On Fri, Sep 6, 2013 at 3:29 AM, Pedro Alves <palves@redhat.com> wrote:
> I'm actually very excited to see gdb and gdbserver sharing
> a single target backend, even if we still have many wrinkles
> in the interfaces to iron out! It does looks like this way
> results in lots of less work, and makes me believe we can
> port other targets to gdbserver already without unsurmountable
> effort.
Do you mean there should be only one structure target_obj in both gdb
and gdbserver?
But I have found that, the structure has been declared different
between gdb and gdbserver, How can I integrate them into single one.
Or just I have got the wrong understand.
--
Yue Lu (陆岳)
prev parent reply other threads:[~2013-09-09 10:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAB8fV=jJ64i91VW52ZmdnEDZhd1ZGTAykDqoFyPJanCP=5beqA@mail.gmail.com>
2013-09-03 8:03 ` [PATCH 2/2] " Yue Lu
2013-09-03 9:38 ` [PATCH 1/2] " Thomas Schwinge
2013-09-03 11:11 ` Pedro Alves
2013-09-03 13:09 ` Thomas Schwinge
2013-09-04 1:47 ` Yue Lu
2013-09-04 1:38 ` Yue Lu
2013-09-05 10:54 ` Yue Lu
2013-09-05 19:29 ` Pedro Alves
2013-09-05 19:39 ` Joel Brobecker
2013-09-05 21:38 ` Thomas Schwinge
2013-09-08 13:35 ` Yue Lu
2013-09-09 9:58 ` Thomas Schwinge
2013-09-18 12:12 ` Pedro Alves
2013-09-18 13:48 ` Yue Lu
2013-09-18 14:52 ` [Hurd/gnu-nat.c] Use ptid_t.lwpid to store, thread ids instead of ptid_t.tid. (was: Re: [PATCH 1/2] Port gdbserver to GNU/Hurd) Pedro Alves
2013-09-18 14:57 ` [PATCH 1/2] Port gdbserver to GNU/Hurd Pedro Alves
2013-09-22 12:58 ` Yue Lu
2013-09-06 18:53 ` Pedro Alves
2013-09-12 3:05 ` Yue Lu
2013-09-18 12:30 ` Pedro Alves
2013-09-18 12:37 ` Pedro Alves
2013-09-19 7:41 ` Yue Lu
2013-09-19 8:30 ` FAIL: gdb.base/nextoverexit.exp: next over exit (the program exited) (was: [PATCH 1/2] Port gdbserver to GNU/Hurd) Thomas Schwinge
2013-09-19 8:44 ` FAIL: gdb.base/nextoverexit.exp: next over exit (the program exited) Pedro Alves
2013-09-09 10:21 ` Yue Lu [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='CAB8fV=hwB_E=5q7o+1AfnJnLiCuG0h_mTy=t8dAttR1+CJ+SmQ@mail.gmail.com' \
--to=hacklu.newborn@gmail.com \
--cc=bug-hurd@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.com \
--cc=palves@redhat.com \
--cc=thomas@codesourcery.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