Re: [GSoC2013] question about "improve the GDB port for GNU Hurd"

Thomas Schwinge
2013-04-30T09:14:00Z

[-- Attachment #1.1: Type: text/plain, Size: 1747 bytes --]

Hi!

On Tue, 30 Apr 2013 00:54:26 +0800, 陆岳 <hacklu.newborn@gmail.com> wrote:
> I am interested in participating GsoC 2013 with GNU Hurd for improve
> the GDB Port for GNU Hurd.

Thanks for your interest!

> Write this email I mainly to identify which work should I do in this
> project. just Port gdbserver or something else?

Well, as I said in the announcement email,
<http://sourceware.org/ml/gdb/2013-04/msg00015.html>, and as reflected on
the project idea page,
<http://www.gnu.org/software/hurd/community/gsoc/project_ideas/gdb.html>,
that is basically up for negotiation with the community, the mentor, and
the student.

> Last may I introduce myself, my name is Yue Lu who is a second-year
> MS student in CS from Tongji University in China. I have worked as a
> FTE in a company which produce embed-device.
> What's plus, I had experience with linux kernel programming. And I
> know GDB was use ptrace to commutate with linux kernel.
> Sadly say, I have't enough knowledge about Hurd, but I have great
> enthusiasm to learn that.

Then I suggest you turn that enthusiasm into productivity ;-) -- install
a GNU/Hurd system,
<http://www.gnu.org/software/hurd/hurd/running/debian.html>, maybe start
with a KVM/QEMU/VirtualBox image, and do a first run of the GDB testsuite
(please locally apply the attached patch to disable some testcases that
currently cause issues as described).
<http://www.gnu.org/software/hurd/open_issues/gdb.html> can help with how
to configure GDB, and so on. In parallel, please get an understanding
how, roughly, the Hurd port of GDB works and interacts with the Hurd
system.

Of course, we're happy to help and answer specific questions.

Grüße,
Thomas

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: disable-some.patch --]
[-- Type: text/x-diff, Size: 1548 bytes --]

diff --git gdb/testsuite/gdb.base/readline.exp gdb/testsuite/gdb.base/readline.exp
index 2acc664..538dcc6 100644
--- gdb/testsuite/gdb.base/readline.exp
+++ gdb/testsuite/gdb.base/readline.exp
@@ -17,6 +17,9 @@

# This file is part of the gdb testsuite.

+untested "<http://www.gnu.org/software/hurd/open_issues/term_blocking.html>"
+return -1
+
#
# Tests for readline operations.
#
diff --git gdb/testsuite/gdb.base/sigall.exp gdb/testsuite/gdb.base/sigall.exp
index 4bd0427..b49fe5b 100644
--- gdb/testsuite/gdb.base/sigall.exp
+++ gdb/testsuite/gdb.base/sigall.exp
@@ -13,6 +13,9 @@
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.

+untested "takes ages: nearly all FAIL with timeout"
+return -1
+
if [target_info exists gdb,nosignals] {
verbose "Skipping sigall.exp because of nosignals."
continue
diff --git gdb/testsuite/gdb.python/py-inferior.exp gdb/testsuite/gdb.python/py-inferior.exp
index ceb0da7..ba98aa8 100644
--- gdb/testsuite/gdb.python/py-inferior.exp
+++ gdb/testsuite/gdb.python/py-inferior.exp
@@ -66,6 +66,9 @@ gdb_breakpoint check_threads
gdb_continue_to_breakpoint "cont to check_threads" ".*pthread_barrier_wait.*"
gdb_test "python print (len (i0.threads ()))" "\r\n9" "test Inferior.threads 2"

+untested "the following tests get the system into an unresponsive state"
+return -1
+
# Proceed to the next test.

gdb_breakpoint [gdb_get_line_number "Break here."]

[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]