This is the mail archive of the
mailing list for the GDB project.
Re: [PATCH V2 0/5] Support tracepoints for ARM linux in GDBServer
- From: Yao Qi <qiyaoltc at gmail dot com>
- To: Antoine Tremblay <antoine dot tremblay at ericsson dot com>
- Cc: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Mon, 7 Nov 2016 09:25:01 +0000
- Subject: Re: [PATCH V2 0/5] Support tracepoints for ARM linux in GDBServer
- Authentication-results: sourceware.org; auth=none
- References: <email@example.com>
On Thu, Nov 3, 2016 at 2:32 PM, Antoine Tremblay
> Since all the prerequisites for this series have been addressed,
> this is a V2 of https://sourceware.org/ml/gdb-patches/2016-01/msg00111.html
All "hard" prerequisites are addressed, but we still want to "teach
unwinders to terminate gracefully in an arch-independent way".
I didn't follow it up closely. I hope we can make progress on this...
"Progress" here means either "it is completely wrong, let us handle
unavailable data in each arch unwinder one by one" or "it is
correct, let us remove these redundant code in each arch".
I am still testing arm-linux gdbserver without and with software
single step. I still see some intermittent regressions _with_
software single step,
+FAIL: gdb.threads/non-stop-fair-events.exp: signal_thread=8: thread 1
broke out of loop (timeout)
+FAIL: gdb.threads/schedlock.exp: schedlock=off: cmd=step: step to
increment (1) (timeout)
This reveals something wrong in software single step in GDBserver.
I don't think we should bring tracepoint in until these regressions are
fixed. I won't work on these regressions until next pre-release. If
you can reproduce them and help to fix them, that will be great.