Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/4] 'catch syscall' feature
Date: Fri, 03 Oct 2008 02:14:00 -0000	[thread overview]
Message-ID: <1223000150.9858.1.camel@miki> (raw)
In-Reply-To: <48E54460.2090401@vmware.com>

Hey Michael :-),

On Thu, 2008-10-02 at 15:00 -0700, Michael Snyder wrote:
> Sérgio Durigan Júnior wrote:
> 
> > On Wed, 2008-10-01 at 16:51 -0700, Michael Snyder wrote:
> > 
> >> I was able to build this, but it failed your test case
> >> (thanks very much for including a test case, by the way).
> >> I'm attaching my failing gdb.log.
> > 
> > Well, maybe you have misunderstood things (or maybe I wasn't clear
> > enough :-)). Currently, my patch only works for 32-bit PowerPC
> > architecture, although I intend to implement the x86 support ASAP.
> 
> Ah, well now I'm embarrassed.   ;-)
> In that case I can't test it, but I can only do "static analysis".

Which is already a pretty good thing. Thanks for that.

> +/* To be used when one needs to know wether a
> +   WSTOPSIG (status) is a syscall */
> 
> "Whether".  And you need a period and two spaces.

Thanks for the correction, and sorry about my bad english (not only in
this case, but in every other). I'll fix this, and I'll add the two
spaces after the period.



> Otherwise, the code looks pretty good, and I like the idea.

Thanks!

-- 
Sérgio Durigan Júnior
Linux on Power Toolchain - Software Engineer
Linux Technology Center - LTC
IBM Brazil


      reply	other threads:[~2008-10-03  2:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30 18:12 Sérgio Durigan Júnior
2008-10-01 22:40 ` Michael Snyder
2008-10-01 23:02   ` Sérgio Durigan Júnior
2008-10-01 23:53     ` Michael Snyder
2008-10-02  3:42       ` Luis Machado
2008-10-02  3:47       ` Sérgio Durigan Júnior
2008-10-02 22:01         ` Michael Snyder
2008-10-03  2:14           ` Sérgio Durigan Júnior [this message]

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=1223000150.9858.1.camel@miki \
    --to=sergiodj@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.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