Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA [PATCH v3] Implement 'catch syscall' for gdbserver
Date: Fri, 27 Sep 2013 20:13:00 -0000	[thread overview]
Message-ID: <1380312832.2237.12.camel@soleil> (raw)
In-Reply-To: <5245DCEC.3060101@redhat.com>

On Fri, 2013-09-27 at 20:30 +0100, Pedro Alves wrote:
> On 09/21/2013 09:55 PM, Philippe Waroquiers wrote:
> 
> > No regression on linux/x86-64, native and gdbserver mode.
> > Manually tested with a (patched) Valgrind gdbserver.
> 
> I guess you've been testing with the native-extended-gdbserver.exp board file?
> I needed these patches to make catch-syscall.exp pass with native-gdbserver.exp
> ("target remote"):
> 
>  https://sourceware.org/ml/gdb-patches/2013-09/msg00968.html
> 
> (I'm still playing with and reviewing the code itself.)
> 
As discussed on IRC, I did the tests with native-gdbserver.exp
but got no failure, as my gdb is compiled without libexpat,
and the failures are only triggered where there is xml support.

Philippe (that will install libexpat one of these days ...)



  reply	other threads:[~2013-09-27 20:13 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-21 20:55 Philippe Waroquiers
2013-09-21 21:03 ` Eli Zaretskii
2013-09-23 11:51 ` Agovic, Sanimir
2013-09-23 19:32   ` Philippe Waroquiers
2013-09-24  7:07     ` Agovic, Sanimir
2013-09-25 16:55       ` Sergio Durigan Junior
2013-09-25 22:55         ` Philippe Waroquiers
2013-09-27 13:25 ` [COMMIT PATCH] remote.c: Remove unnecessary fields from 'struct stop_reply'. (was: Re: RFA [PATCH v3] Implement 'catch syscall' for gdbserver) Pedro Alves
2013-09-27 19:30 ` RFA [PATCH v3] Implement 'catch syscall' for gdbserver Pedro Alves
2013-09-27 20:13   ` Philippe Waroquiers [this message]
2013-09-27 20:55 ` Sergio Durigan Junior
2013-09-29 15:04   ` RFA [PATCH v4] Implement 'catch syscall' for gdbserver (was Re: RFA [PATCH v3] Implement 'catch syscall' for gdbserver) Philippe Waroquiers
2013-10-01  5:16     ` Sergio Durigan Junior
2013-10-02 21:02       ` Sergio Durigan Junior
2013-10-02 19:41     ` Always run the PTRACE_O_TRACESYSGOOD tests even if PTRACE_O_TRACEFORK is not supported. (was: Re: RFA [PATCH v4] " Pedro Alves
2013-10-02 22:08       ` Philippe Waroquiers
2013-10-03 10:16         ` Always run the PTRACE_O_TRACESYSGOOD tests even if PTRACE_O_TRACEFORK is not supported Pedro Alves
2013-10-03 18:40     ` RFA [PATCH v4] Implement 'catch syscall' for gdbserver (was Re: RFA [PATCH v3] Implement 'catch syscall' for gdbserver) Pedro Alves
2013-10-03 19:53       ` Tom Tromey
2013-10-04 17:41         ` Pedro Alves
2013-10-03 22:02       ` Philippe Waroquiers
2013-10-04 17:29         ` Pedro Alves
2013-10-05  9:15           ` Pedro Alves
2013-10-09 21:54             ` Philippe Waroquiers
2013-10-09 22:05               ` Sergio Durigan Junior
2013-10-09 22:09                 ` Philippe Waroquiers
2013-10-04  4:22     ` Luis Machado
2013-10-04 17:40       ` Pedro Alves
2013-10-04 18:55         ` Stan Shebs
2013-10-07 19:07           ` Pedro Alves

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=1380312832.2237.12.camel@soleil \
    --to=philippe.waroquiers@skynet.be \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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