From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: jan.kratochvil@redhat.com (Jan Kratochvil)
Cc: mark.kettenis@xs4all.nl (Mark Kettenis),
drow@false.org, tromey@redhat.com (Tom Tromey),
gdb-patches@sourceware.org
Subject: Re: [patch] Fix i386 memory-by-register access on amd64
Date: Mon, 13 Jul 2009 18:10:00 -0000 [thread overview]
Message-ID: <200907131708.n6DH896H016447@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20090708144136.GA6490@host0.dyn.jankratochvil.net> from "Jan Kratochvil" at Jul 08, 2009 04:41:37 PM
Jan Kratochvil wrote:
> Therefore fixed linux_xfer_partial. Therefore it no longer needs the fix to
> be present also in inf_ptrace_xfer_partial. I do not know how non-Linux OSes
> handle the debugging of 32bit inferior on 64bit GDB so I have no opinion
> whether the inf_ptrace_xfer_partial patch makes sense, i can drop it.
I think at this point it would probably be better to just to the Linux fix.
I've looked at a couple of ptrace implementations in the Linux kernel, and
it seems this fix should be correct on all bi-arch Linux platforms.
I simply do not know enough how ptrace behaves on other OSes -- until we
get a specific bug report on some other OS, I think we should leave the
behaviour unchanged for now.
> 2009-07-08 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> Fix memory access from signed 32bit inferior registers on 64bit GDB.
> * inf-ptrace.c (inf_ptrace_xfer_partial <TARGET_OBJECT_MEMORY>): New
> variable addr_bit. Mask OFFSET by the ADDR_BIT width.
> * linux-nat.c (linux_xfer_partial <TARGET_OBJECT_MEMORY>): Likewise.
>
> 2009-07-08 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * gdb.arch/amd64-i386-address.exp, gdb.arch/amd64-i386-address.S: New.
The linux-nat.c change and the test case are OK.
Thanks,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2009-07-13 17:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 10:27 Jan Kratochvil
2009-04-29 19:05 ` Mark Kettenis
2009-04-29 20:29 ` Jan Kratochvil
2009-04-29 20:45 ` Jan Kratochvil
2009-06-25 16:33 ` Tom Tromey
2009-07-06 8:19 ` Jan Kratochvil
2009-07-07 16:24 ` Ulrich Weigand
2009-07-07 16:54 ` Daniel Jacobowitz
2009-07-07 18:00 ` Mark Kettenis
2009-07-07 18:22 ` Jan Kratochvil
2009-07-07 18:43 ` Mark Kettenis
2009-07-08 13:20 ` [patch] /* */ for target_thread_architecture [Re: [patch] Fix i386 memory-by-register access on amd64] Jan Kratochvil
2009-07-09 12:51 ` Ulrich Weigand
2009-07-09 16:36 ` Jan Kratochvil
2009-07-08 14:42 ` [patch] Fix i386 memory-by-register access on amd64 Jan Kratochvil
2009-07-13 18:10 ` Ulrich Weigand [this message]
2009-07-13 19:42 ` Mark Kettenis
2009-07-13 20:32 ` Jan Kratochvil
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=200907131708.n6DH896H016447@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mark.kettenis@xs4all.nl \
--cc=tromey@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