From: Daniel Jacobowitz <drow@false.org>
To: Jose Flavio Aguilar Paulino <jflavio@br.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 24700]
Date: Thu, 01 Mar 2007 18:37:00 -0000 [thread overview]
Message-ID: <20070301183700.GA19796@caradoc.them.org> (raw)
In-Reply-To: <1172777198.10229.11.camel@kadinsky.prado>
On Thu, Mar 01, 2007 at 03:26:38PM -0400, Jose Flavio Aguilar Paulino wrote:
> This patch modifies the <gdb/ppc-linux-tdep.c> file.
> It was noticed in GDB for PPC64 that the command "set var" failed when
> used to change a string value, the intent of this patch is to solve this
> gdb64's problem. Ex:
>
> char *ptr = NULL;
> printf("ptr string is %s\n", ptr);
> (gdb) set var ptr="def"
> ---Problem Description---
> gdb64: failed to set a string variable's value.
>
> I could not detect any regressions that could be caused by this patch in GDB's testsuite.
What is the problem, and how did the patch fix it? There are a number
of style issues with the patch, but no point at looking at them until
we understand the overall issue.
> + if (targ != ¤t_target)
> + return get_target_memory_unsigned (targ, addr2deref, 8);
> + else
> + {
> + gdb_assert (8 <= sizeof (buf));
> + target_read_memory(addr, buf, 8);
> + return extract_unsigned_integer (buf, 8);
> + }
What's the point of special casing based on the target?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-03-01 18:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 18:27 Jose Flavio Aguilar Paulino
2007-03-01 18:37 ` Daniel Jacobowitz [this message]
2007-03-01 20:06 ` Jose Flavio Aguilar Paulino
2007-03-01 20:40 ` Daniel Jacobowitz
2007-03-01 21:56 ` Thiago Jung Bauermann
2007-03-01 22:03 ` Daniel Jacobowitz
2007-03-01 22:28 ` Thiago Jung Bauermann
2007-03-01 22:47 ` Andreas Schwab
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=20070301183700.GA19796@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jflavio@br.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