From: Pedro Alves <pedro@codesourcery.com>
To: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
Cc: Daniel Jacobowitz <drow@false.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4] catch syscall -- try 4 -- Architecture-independent part
Date: Mon, 09 Mar 2009 18:39:00 -0000 [thread overview]
Message-ID: <200903091839.50051.pedro@codesourcery.com> (raw)
In-Reply-To: <1236611364.12452.7.camel@miki>
On Monday 09 March 2009 15:09:24, Sérgio Durigan Júnior wrote:
> if (catch_syscall_enabled () > 0) ...
>
> What happens is that the code does not freeze. GDB still works with
> this, and as far as I could investigate it shows everything fine.
> Therefore, I think this function is not needed at all.
Oh, was that because you're only enabling PTRACE_O_TRACESYSGOOD
after startup_inferior is finished, in linux_child_post_startup_inferior,
and, PT_SYSCALL just behaves as PT_CONTINUE in that case? That
would make sense to me.
--
Pedro Alves
next prev parent reply other threads:[~2009-03-09 18:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 0:31 Sérgio Durigan Júnior
2009-01-26 0:51 ` Pedro Alves
2009-01-26 4:56 ` Sérgio Durigan Júnior
2009-01-26 17:04 ` Sérgio Durigan Júnior
2009-02-01 19:33 ` Daniel Jacobowitz
2009-02-25 21:44 ` Sérgio Durigan Júnior
2009-02-28 0:44 ` Daniel Jacobowitz
2009-03-08 18:16 ` Sérgio Durigan Júnior
2009-03-09 13:19 ` Daniel Jacobowitz
2009-03-09 14:09 ` Sérgio Durigan Júnior
2009-03-09 18:39 ` Pedro Alves [this message]
2009-03-09 18:56 ` Daniel Jacobowitz
2009-03-09 18:31 ` Pedro Alves
2009-03-29 21:16 ` Sérgio Durigan Júnior
2009-03-31 16:39 ` Daniel Jacobowitz
2009-04-09 19:29 ` Sérgio Durigan Júnior
2009-04-09 19:36 ` Daniel Jacobowitz
2009-04-09 20:21 ` Sérgio Durigan Júnior
2009-04-15 23:12 ` Sérgio Durigan Júnior
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=200903091839.50051.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@linux.vnet.ibm.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