From: 陆岳 <hacklu.newborn@gmail.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: gdb@sourceware.org, bug-hurd@gnu.org
Subject: Re: [GSoC2013] question about "improve the GDB port for GNU Hurd"
Date: Thu, 02 May 2013 12:50:00 -0000 [thread overview]
Message-ID: <CAB8fV=ikqozPTBF4e=Udu=HNjxx+Un6SU0M9czi5UaSLu+zwRw@mail.gmail.com> (raw)
In-Reply-To: <87ehdpsip3.fsf@kepler.schwinge.homeip.net>
Thank you for providing the requested information.
On Thu, May 2, 2013 at 7:51 PM, Thomas Schwinge <thomas@codesourcery.com> wrote:
> You can clone hurd/web.git repository from Savannah, and check out the
> toolchain/logs/master branch (which I have as a Git submodule on
> toolchain/logs), and compare the
> gdb/coulomb.SCHWINGE/test/gdb/testsuite/gdb.*/*.sum files with those you
> got.
I will do the compare after I have finished the application.
> Which are the handful of files in the GDB sources that are relevant
> (only) for the native GNU Hurd support?
To my knowledge now, there are at least gnu-nat.c, i386gnu-tdep.c,
gnu-nat.h and i386gnu-nat.c relating with GNU Hurd support.
> Yes, this shows you actually did look at the sources, trying to figure
> out how it works, and what you describe is correct in principle.
> (Leaving out many details, of course.) As you're still new to the Hurd's
> architecture, based on Mach's RPC system, it is no wonder that the
> message transport is still not completely clear to you -- that will get
> better with time, as you learn more about it.
yeah, I will continue to learn more about GNU Hurd. By the way, Last
night I have found a useful document
in this ftp(ftp://ftp.cs.cmu.edu/afs/cs/project/mach/public/doc/unpublished/exception.doc)
which explained how the GDB take advantage of Mach's exception
facility.
> No, please use the knowledge you got by now to write your application,
> and send it in, which needs to happen tomorrow. Then, in the next
> week(s), we can still continue refining it, and you could, for example,
> prepare and send a first patch for GDB for the issue that you reported on
> IRC: so that the configure process stops with an error if targeting GNU
> Hurd and the MIG tool was not found. (gdb/configure.ac is the file you
> need to edit, and then regenerate gdb/configure.)
I will write my application right now. And the patch is on the way,
this afternoon I have already read some How-to about autoconf.
Best Regards.
--
Yue Lu (陆岳)
next prev parent reply other threads:[~2013-05-02 12:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAB8fV=js9NvAp3Q079cNT=0=yoiLcjOWNQFyD4LhaScB=M4mSQ@mail.gmail.com>
2013-04-30 9:14 ` Thomas Schwinge
2013-05-01 12:26 ` 陆岳
2013-05-02 11:52 ` Thomas Schwinge
2013-05-02 12:50 ` 陆岳 [this message]
2013-05-10 10:35 ` Thomas Schwinge
2013-05-10 14:31 ` Hacklu
2013-05-23 2:16 ` Yue Lu
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=ikqozPTBF4e=Udu=HNjxx+Un6SU0M9czi5UaSLu+zwRw@mail.gmail.com' \
--to=hacklu.newborn@gmail.com \
--cc=bug-hurd@gnu.org \
--cc=gdb@sourceware.org \
--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