From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Ulrich Weigand <uweigand@de.ibm.com>,
GDB Patches <gdb-patches@sourceware.org>,
Markus Deuling <deuling@de.ibm.com>
Subject: Re: [rfc] [13/17] Get rid of current_gdbarch in win32-nat.c
Date: Thu, 11 Oct 2007 17:59:00 -0000 [thread overview]
Message-ID: <20071011175153.GA443@ednor.casa.cgf.cx> (raw)
In-Reply-To: <470DE4B6.1050708@de.ibm.com>
On Thu, Oct 11, 2007 at 10:54:14AM +0200, Markus Deuling wrote:
> this patch gets rid of some of the current_gdbarch's in win32-nat.c. Maybe
> someone can test this? I have no idea how to :-)
> Thanks a lot. Is this ok to commit?
>
> ChangeLog:
>
> * win32-nat.c (do_win32_fetch_inferior_registers, win32_resume)
> (do_win32_store_inferior_registers): Use get_regcache_arch to get at
> the current architecture by regcache.
I'm sorry. I'm a little confused. If you're offering a patch why can't
you test it? Wouldn't that be considered a prerequisite for a patch?
cgf
next prev parent reply other threads:[~2007-10-11 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 8:55 Markus Deuling
2007-10-11 17:59 ` Christopher Faylor [this message]
2007-10-22 6:09 ` Markus Deuling
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=20071011175153.GA443@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=deuling@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.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