From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <qiyaoltc@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [RFC] Support command "catch syscall" properly on different targets
Date: Tue, 03 Mar 2015 18:06:00 -0000 [thread overview]
Message-ID: <87bnkaklbe.fsf@redhat.com> (raw)
In-Reply-To: <54F5A90E.8050704@redhat.com> (Pedro Alves's message of "Tue, 03 Mar 2015 12:29:02 +0000")
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.
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".
--
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2015-03-03 18:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 14:23 Yao Qi
2015-02-27 18:49 ` Doug Evans
2015-03-03 11:56 ` Yao Qi
2015-03-03 12:14 ` Pedro Alves
2015-02-27 18:50 ` Pedro Alves
2015-03-03 12:06 ` Yao Qi
2015-03-03 12:38 ` Pedro Alves
2015-02-27 21:04 ` Sergio Durigan Junior
2015-03-03 12:11 ` Yao Qi
2015-03-03 12:29 ` Pedro Alves
2015-03-03 18:06 ` Sergio Durigan Junior [this message]
2015-03-03 18:18 ` Pedro Alves
2015-03-06 16:36 ` Yao Qi
2015-03-06 22:04 ` Sergio Durigan Junior
2015-03-09 14:29 ` Yao Qi
2015-03-10 4:53 ` Sergio Durigan Junior
2015-03-09 14:10 ` Yao Qi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bnkaklbe.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=qiyaoltc@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).