[PATCH] Fix for PR breakpoints/16297: Fix catch syscall to work with syscall 0

[Pedro Alves]

On 12/15/2013 04:04 AM, Sergio Durigan Junior wrote:
> On Sunday, December 15 2013, Gabriel Krisman Bertazi wrote:
> 
>> This is a fix for bug 16297. The problem occurs when the user attempts
>> to catch any syscall 0 (such as syscall read on Linux/x86_64). GDB was
>> not able to catch the syscall and was missing the breakpoint.
>>
>> Now, breakpoint_hit_catch_syscall returns immediately when it finds the
>> correct syscall number, avoiding a following check for the end of the
>> search vector, that returns a no hit if the syscall number was zero.
> 
> Thanks.
> 
> Just for the record, I pre-reviewed Krisman's patch and it's OK.  I am
> also helping him in obtaining the copyright assignment.

Thanks you both.  FAOD, this is OK.

> I will send a patch to test this feature as soon as my other patch
> (which touches catch-syscall.exp and improves it) gets approved.

-- 
Pedro Alves