[Bug gdb/12465] New: catch syscall yields garbage on syscall return.

["ddaney at caviumnetworks dot com" <sourceware-bugzilla at sourceware dot org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=12465

           Summary: catch syscall yields garbage on syscall return.
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
        AssignedTo: unassigned@sourceware.org
        ReportedBy: ddaney@caviumnetworks.com


On mips*-linux* the register used to communicate the syscall number is
clobbered by the kernel by the time we stop on the syscall return.  This causes
gdb to not be able to figure out which syscall is returning and it prints out
erroneous information about the syscall type .

There are two possibilities when a syscall is entered by a thread:

1) It returns.

2) The thread terminates.

In the first case we could remember the syscall number from the syscall entry. 
For the second case we don't care as we never hit the syscall return.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.