From: Luis Machado <luisgpm@linux.vnet.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 0/1] Threaded Watchpoints
Date: Mon, 10 Sep 2007 15:34:00 -0000 [thread overview]
Message-ID: <1189438454.4318.9.camel@localhost> (raw)
In-Reply-To: <20070910002103.GA25048@caradoc.them.org>
> Here is my current patch. The PowerPC bits are totally untested,
> not even compiled - could you test it for me, please? I don't
> have a suitable system.
Sure, i'll do the tests as soon as i get the code to compile.
> I've regression tested i386, amd64, and ia64. I tested S/390 by hand
> and it works, but the extra logic in watchthreads.exp for that
> platform hasn't been tested (no DejaGNU or expect on my test system).
I couldn't build the code for ppc due to a call to the "save_siginfo"
function. Why is exactly that function's been moved to "linux-nat.c"? It
seems that it's being called only in that file, and with a PPC-specific
ptrace request "PTRACE_GETSIGINFO", which is not declared anywhere
except for "ppc-linux-nat.c".
Could you please clarify this specific point?
Thanks!
Regards,
--
Luis Machado
IBM Linux Technology Center
e-mail: luisgpm@linux.vnet.ibm.com
next prev parent reply other threads:[~2007-09-10 15:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 13:51 Luis Machado
2007-08-20 17:33 ` Luis Machado
2007-08-20 17:40 ` Luis Machado
2007-09-05 2:04 ` Daniel Jacobowitz
2007-09-05 12:31 ` Luis Machado
2007-09-10 0:21 ` Daniel Jacobowitz
2007-09-10 15:34 ` Luis Machado [this message]
2007-09-10 15:44 ` Daniel Jacobowitz
2007-09-10 17:56 ` Luis Machado
2007-09-10 18:30 ` Daniel Jacobowitz
2007-09-10 18:23 ` Ulrich Weigand
2007-09-10 18:29 ` Daniel Jacobowitz
2007-09-10 18:44 ` Ulrich Weigand
2007-09-10 18:54 ` Daniel Jacobowitz
2007-09-10 19:03 ` Ulrich Weigand
2007-09-10 19:12 ` Daniel Jacobowitz
2007-09-10 19:31 ` Mark Kettenis
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=1189438454.4318.9.camel@localhost \
--to=luisgpm@linux.vnet.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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