Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [RFA] Fix setting of VSX registers
Date: Thu, 22 Jul 2010 16:06:00 -0000	[thread overview]
Message-ID: <m3lj935wo1.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1279738729.11022.23.camel@hactar> (Thiago Jung Bauermann's	message of "Wed, 21 Jul 2010 15:58:49 -0300")

>>>>> "Thiago" == Thiago Jung Bauermann <bauerman@br.ibm.com> writes:

Thiago> The problem is, the function was "fetching" the VSX registers using
Thiago> PTRACE_SETVSXREGS instead of PTRACE_GETVSXREGS. Ouch.

I don't know this code at all, but this change seems obviously ok to me.

Thiago> This patch fixes the typo, and also fixes the vsx-regs.exp testcase to
Thiago> use gdb_test instead of send_gdb (this also fixes some synchronization
Thiago> issues in the test), and updates the expect info reg output with the new
Thiago> v2_double member.

I don't understand why the new gdb_test calls have an empty "message"
argument.

Actually, this code in gdb_test itself looks somewhat bogus.
Aside from parsing arguments by hand (why??), it uses a different
default for the message than gdb_test_multiple.  I don't understand when
this can ever be the right thing to do.

For your patch I suggest just leaving off the 3rd argument.

Also, when the second argument to gdb_test is the empty string ... I
suspect you actually want to use gdb_test_no_output.

Tom


  reply	other threads:[~2010-07-22 16:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-21 18:59 Thiago Jung Bauermann
2010-07-22 16:06 ` Tom Tromey [this message]
2010-07-26 17:31   ` Thiago Jung Bauermann
2010-07-27 15:20     ` Joel Brobecker
2010-07-27 16:14       ` Thiago Jung Bauermann
2010-07-28 21:34     ` Tom Tromey
2010-07-28 21:43       ` Joel Brobecker
2010-07-28 21:57         ` Tom Tromey
2010-08-18 21:18   ` Thiago Jung Bauermann
2010-08-19  9:50     ` Joel Brobecker
2010-08-19 17:56       ` Thiago Jung Bauermann

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=m3lj935wo1.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=bauerman@br.ibm.com \
    --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