Enable GDB's fast and static tracepoint capabilities for the PowerPC target by implementing the required target-dependent gdbserver support for the in-process agent.
The goal is that the fast and static tracepoint tests in gdb.trace pass on powerpc64-linux. Note that some of the tests will themselves require porting.
There's a $3,200 bounty on this issue: https://www.bountysource.com/issues/3483549-implement-gdbserver-in-process-agent-for-powerpc
The fast tracepoint patches have landed. Anything left to do here?
Just as discussed in Bug #18377, static tracepoints don't work anywhere right now, so implementing fast tracepoints suffices for now. Thanks for implementing this!
thank you for the insights in resolving this bug. https://www.remorquage-depannage-auto-lehavre76.com
A GDB 7.6.2 release should be created to help users switching to binutils 2.24 have an official release they can use. And for the record, GDB 7.7 will also support binutils 2.2.4 https://worcesterroofingandsiding.com
For the test, in this case, checking that command echo still works is
sufficient. Comparing stty output before/after running GDB is even
better. Because stty may not be available, the test tries both ways.
In any case, since expect's spawn (what we use to start gdb) creates a
new pseudo tty, another expect spawn or tcl exec after GDB exits would
not see the wrong terminal settings. https://concretesolutionsofbuffalo.com