Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Regression for gdbserver  [Re: [PATCH] Linux/gdbserver: Fix memory read ptrace fallback issues]
Date: Tue, 22 May 2012 08:04:00 -0000	[thread overview]
Message-ID: <20120522080321.GA18378@host2.jankratochvil.net> (raw)
In-Reply-To: <alpine.DEB.1.10.1205220050470.11227@tp.orcam.me.uk>

On Tue, 22 May 2012 02:05:28 +0200, Maciej W. Rozycki wrote:
>  Applied now, thanks for the review.

272cb31d810a541dcc44f942fabb3167580b838e is the first bad commit
commit 272cb31d810a541dcc44f942fabb3167580b838e
Author: Maciej W. Rozycki <macro@linux-mips.org>
Date:   Mon May 21 23:50:25 2012 +0000

    	* linux-low.c (linux_store_registers): Don't re-retrieve data
    	with ptrace that has already been obtained from /proc.  Always
    	copy any data retrieved with ptrace to the buffer supplied.

-PASS: gdb.mi/gdb701.exp: list children of fooPtr
+FAIL: gdb.mi/gdb701.exp: list children of fooPtr
-PASS: gdb.mi/mi2-var-child.exp: VT: list children of ptr2.*ptr.1_anonymous
+FAIL: gdb.mi/mi2-var-child.exp: VT: list children of ptr2.*ptr.1_anonymous
-PASS: gdb.mi/mi2-var-child.exp: VT: create root varobj for v
-PASS: gdb.mi/mi2-var-child.exp: VT: list children of v3
-PASS: gdb.mi/mi2-var-child.exp: path expression for v3
-PASS: gdb.mi/mi2-var-child.exp: expression for v3
-PASS: gdb.mi/mi2-var-child.exp: path expression for v3.x
-PASS: gdb.mi/mi2-var-child.exp: expression for v3.x
-PASS: gdb.mi/mi2-var-child.exp: VT: list children of v3.1_anonymous
-PASS: gdb.mi/mi2-var-child.exp: path expression for v3.1_anonymous
-PASS: gdb.mi/mi2-var-child.exp: expression for v3.1_anonymous
-PASS: gdb.mi/mi2-var-child.exp: VT: list children of v3.2_anonymous
-PASS: gdb.mi/mi2-var-child.exp: path expression for v3.2_anonymous
-PASS: gdb.mi/mi2-var-child.exp: expression for v3.2_anonymous
-PASS: gdb.mi/mi2-var-child.exp: path expression for v3.1_anonymous.a
-PASS: gdb.mi/mi2-var-child.exp: expression for v3.1_anonymous.a
-PASS: gdb.mi/mi2-var-child.exp: path expression for v3.2_anonymous.b
-PASS: gdb.mi/mi2-var-child.exp: expression for v3.2_anonymous.b
+FAIL: gdb.mi/mi2-var-child.exp: VT: create root varobj for v
+FAIL: gdb.mi/mi2-var-child.exp: VT: list children of v3
+FAIL: gdb.mi/mi2-var-child.exp: path expression for v3
+FAIL: gdb.mi/mi2-var-child.exp: expression for v3
+FAIL: gdb.mi/mi2-var-child.exp: path expression for v3.x
+FAIL: gdb.mi/mi2-var-child.exp: expression for v3.x
+FAIL: gdb.mi/mi2-var-child.exp: VT: list children of v3.1_anonymous
+FAIL: gdb.mi/mi2-var-child.exp: path expression for v3.1_anonymous
+FAIL: gdb.mi/mi2-var-child.exp: expression for v3.1_anonymous
+FAIL: gdb.mi/mi2-var-child.exp: VT: list children of v3.2_anonymous
+FAIL: gdb.mi/mi2-var-child.exp: path expression for v3.2_anonymous
+FAIL: gdb.mi/mi2-var-child.exp: expression for v3.2_anonymous
+FAIL: gdb.mi/mi2-var-child.exp: path expression for v3.1_anonymous.a
+FAIL: gdb.mi/mi2-var-child.exp: expression for v3.1_anonymous.a
+FAIL: gdb.mi/mi2-var-child.exp: path expression for v3.2_anonymous.b
+FAIL: gdb.mi/mi2-var-child.exp: expression for v3.2_anonymous.b
(many more, I did not list them all)

 888-interpreter-exec console "set $pc=0x0"^M
-888^done^M
+=thread-group-exited,id="i1"^M
+&"Remote connection closed\n"^M
+888^error,msg="Remote connection closed"^M
 (gdb) ^M
-PASS: gdb.mi/mi-cli.exp: -interpreter-exec console "set $pc=0x0"
+FAIL: gdb.mi/mi-cli.exp: -interpreter-exec console "set $pc=0x0"

 -var-list-children fooPtr^M
+=thread-group-exited,id="i1"^M
 ^done,numchild="3",children=[child={name="fooPtr.x",exp="x",numchild="0",type="int",thread-id="1"},child={name="fooPtr.y",exp="y",numchild="0",type="int",thread-id="1"},child={name="fooPtr.z",exp="z",numchild="0",type="int",thread-id="1"}],has_more="0"^M
 (gdb) ^M
-PASS: gdb.mi/gdb701.exp: list children of fooPtr
+FAIL: gdb.mi/gdb701.exp: list children of fooPtr

 -var-create v3 * v^M
-^done,name="v3",numchild="3",value="{...}",type="struct {...}",thread-id="1",has_more="0"^M
+^error,msg="-var-create: unable to create variable object"^M
 (gdb) ^M
-PASS: gdb.mi/mi2-var-child.exp: VT: create root varobj for v
+FAIL: gdb.mi/mi2-var-child.exp: VT: create root varobj for v

etc. etc.


  reply	other threads:[~2012-05-22  8:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16 22:57 [PATCH] Linux/gdbserver: Fix memory read ptrace fallback issues Maciej W. Rozycki
2012-05-18 16:53 ` Pedro Alves
2012-05-18 18:46   ` Maciej W. Rozycki
2012-05-18 20:11     ` Pedro Alves
2012-05-22  0:05       ` Maciej W. Rozycki
2012-05-22  8:04         ` Jan Kratochvil [this message]
2012-05-22 12:43           ` Regression for gdbserver [Re: [PATCH] Linux/gdbserver: Fix memory read ptrace fallback issues] Maciej W. Rozycki
2012-05-22 19:35             ` [patch] " Jan Kratochvil
2012-05-22 20:06               ` Maciej W. Rozycki
2012-05-22 20:42                 ` Jan Kratochvil
2012-05-22 23:34                   ` Maciej W. Rozycki
2012-05-23  5:29                     ` 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=20120522080321.GA18378@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@codesourcery.com \
    --cc=palves@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