[Bug server/17221] New: Implement gdbserver in-process agent for PowerPC

[Bug server/17221] New: Implement gdbserver in-process agent for PowerPC

[uweigand at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=17221

            Bug ID: 17221
           Summary: Implement gdbserver in-process agent for PowerPC
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: server
          Assignee: unassigned at sourceware dot org
          Reporter: uweigand at gcc dot gnu.org

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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug server/17221] Implement gdbserver in-process agent for PowerPC

[community at bountysource dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=17221

Bountysource <community at bountysource dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |community at bountysource dot com

--- Comment #1 from Bountysource <community at bountysource dot com> ---
There's a $3,200 bounty on this issue:
https://www.bountysource.com/issues/3483549-implement-gdbserver-in-process-agent-for-powerpc

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug server/17221] Implement gdbserver in-process agent for PowerPC

[bap.fayol at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=17221

yaoltreza <bap.fayol at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bap.fayol at gmail dot com

--- Comment #5 from yaoltreza <bap.fayol at gmail dot com> ---
thank you for the insights in resolving this bug.
https://www.remorquage-depannage-auto-lehavre76.com

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug server/17221] Implement gdbserver in-process agent for PowerPC

[richardsjenkins70 at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=17221

Joey Kim <richardsjenkins70 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |richardsjenkins70 at gmail dot com

--- Comment #6 from Joey Kim <richardsjenkins70 at gmail dot 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

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug server/17221] Implement gdbserver in-process agent for PowerPC

[johnsjvi95 at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=17221

Stewart <johnsjvi95 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |johnsjvi95 at gmail dot com

--- Comment #7 from Stewart <johnsjvi95 at gmail dot 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

-- 
You are receiving this mail because:
You are on the CC list for the bug.