This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC] Support command "catch syscall" properly on different targets


On 03/03/2015 06:06 PM, Sergio Durigan Junior wrote:
> On Tuesday, March 03 2015, Pedro Alves wrote:
> 
>> On 03/03/2015 12:11 PM, Yao Qi wrote:
>>> Sergio Durigan Junior <sergiodj@redhat.com> writes:
>>>
>>>> You mean it's possible to use "catch syscall" on HP-UX targets?  I
>>>> wonder how it works.
>>>
>>> Yes, that is what I meant, at least that is what I can tell from the
>>> source.
>>
>> TARGET_WAITKIND_SYSCALL_ENTRY / TARGET_WAITKIND_SYSCALL_RETURN
>> was supported by the HP-UX target long before GNU/Linux gained
>> support.  See inf-ttrace.c.  However, I don't think "catch syscall"
>> itself ever did.  inf_ttrace_enable_syscall_events is only used
>> for watchpoints.  Not that I find we should go fix it, mind you.
> 
> Exactly, that's what I meant by my question.  Sorry for not being
> clear.
> 

Ahah, looks like we've been through this before:

  https://sourceware.org/ml/gdb-patches/2013-12/msg00587.html

I apologize on behalf of my former self.  He was silly.  :-)

> I remember seeing TARGET_WAITKIND_SYSCALL_{ENTRY,RETURN} when
> implementing "catch syscall", and I even remember making a decision to
> use them instead of creating other TARGET_WAITKIND's.  However, the
> "catch syscall" itself doesn't work on HP-UX.
> 
> Anyway, I just raised this point because we shouldn't "return 1" when
> asked if inf-ttrace.c supports "catch syscall".

Yeah.  In any case, AFAIR, we were going to remove support for hpux,
as nobody really cares about it anymore...

Thanks,
Pedro Alves


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]