From: Yao Qi <qiyaoltc@gmail.com>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [patch 0/3, nios2] unbreak nios2-linux-gnu GDB
Date: Tue, 28 Apr 2015 11:15:00 -0000 [thread overview]
Message-ID: <86iocgwmb5.fsf@gmail.com> (raw)
In-Reply-To: <55393E8C.8090804@codesourcery.com> (Sandra Loosemore's message of "Thu, 23 Apr 2015 12:48:44 -0600")
Sandra Loosemore <sandra@codesourcery.com> writes:
> GDB support for nios2-linux-gnu became broken during the time when
> glibc and kernel support for that target was transitioning to the
> upstream repositories. Both ports were accepted around the first of
> the year, but then the initial 3.19 kernel was not usable for testing
> due to some unrelated problems with the ethernet support, it took a
> long time to track down a bug that caused a kernel hang, and then we
> ran into some additional bugs with kernel cache flushing. The icache
> flush issues were fixed in time for the 4.0 kernel release and GDB is
> working pretty well with that kernel version now for manual use, but
> to get consistent results from automated testing I had to apply an
> additional local patch to flush the dcache more aggressively. I
> expect some version of that will make it into future kernel releases
> since Altera is aware of the trouble now.
In short, with your patches applied, GDB/GDBserver should work well with
kernel 4.0 release (with your local patch to flush dcache), is it a
correct statement? Do you have a GDB test summary (number of PASS and
FAIL) to show how well it does now?
>
> There are 3 patches:
>
> (1) revert to using "trap 31" for breakpoints
> (2) use PTRACE_GETREGSET/SETREGSET in gdbserver
> (3) fixes for new implementation of signal handler trampolines
>
> Since the old out-of-tree kernel/glibc ports are now obsolete, we
> haven't tried to maintain backward compatibility in these patches.
I think we need a NEWS entry for this change.
>
> Yao, I noticed that you haven't updated your e-mail address in
> MAINTAINERS; are you still acting as nios2 maintainer?
ARM and Linaro isn't against me to reviewing nios2 gdb patches with my
gmail address, so I think I can still review them.
--
Yao (齐尧)
next prev parent reply other threads:[~2015-04-28 10:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 18:49 Sandra Loosemore
2015-04-23 18:53 ` [patch 1/3, nios2] revert to using "trap 31" for breakpoints Sandra Loosemore
2015-04-28 11:18 ` Yao Qi
2015-04-23 18:55 ` [patch 2/3, nios2] use PTRACE_GETREGSET/SETREGSET in gdbserver Sandra Loosemore
2015-04-28 11:29 ` Yao Qi
2015-04-28 11:31 ` Pedro Alves
2015-04-28 15:27 ` Sandra Loosemore
2015-04-23 19:01 ` [patch 3/3, nios2] fixes for new implementation of signal handler trampolines Sandra Loosemore
2015-04-23 19:11 ` Sandra Loosemore
2015-04-28 12:11 ` Yao Qi
2015-04-28 15:47 ` Sandra Loosemore
2015-04-28 11:15 ` Yao Qi [this message]
2015-04-28 15:14 ` [patch 0/3, nios2] unbreak nios2-linux-gnu GDB Sandra Loosemore
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=86iocgwmb5.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=sandra@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).