Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Re: [patch] XFAIL gdb.cp/mb-inline.exp conditionaly
Date: Thu, 23 Jun 2011 14:41:00 -0000	[thread overview]
Message-ID: <4E035078.5070205@codesourcery.com> (raw)
In-Reply-To: <201106231137.03657.pedro@codesourcery.com>

[-- Attachment #1: Type: text/plain, Size: 572 bytes --]

On 06/23/2011 06:37 PM, Pedro Alves wrote:
> On Thursday 23 June 2011 10:21:21, Yao Qi wrote:
>>         gdb/testsuite/
>>         * gdb.cp/mb-inline.exp: Parse the output of `info break' to check breakpoint
>>         1.2 is disabled.  XFAIL for uclinux.
> 
> If you don't want to fix gdb for this now, then please open a PR, and
> make it a kfail instead.  Okay with that change.
> 

A PR is opened http://sourceware.org/bugzilla/show_bug.cgi?id=12924.

Patch attached is what I committed.

http://sourceware.org/ml/gdb-cvs/2011-06/msg00139.html

-- 
Yao (齐尧)

[-- Attachment #2: mb-inline-v2.patch --]
[-- Type: text/x-patch, Size: 1105 bytes --]

	gdb/testsuite/
	* gdb.cp/mb-inline.exp: Parse the output of `info break' to check breakpoint
	1.2 is disabled.  KFAIL for uclinux.

diff --git a/gdb/testsuite/gdb.cp/mb-inline.exp b/gdb/testsuite/gdb.cp/mb-inline.exp
index 86cb5ba..81f7460 100644
--- a/gdb/testsuite/gdb.cp/mb-inline.exp
+++ b/gdb/testsuite/gdb.cp/mb-inline.exp
@@ -101,7 +101,19 @@ gdb_expect {
     }
 }
 
-gdb_continue_to_end "disabled breakpoint 1.2"
+gdb_test_multiple "info break" "disabled breakpoint 1.2" {
+    -re "1\.2.* n .* at .*$hdrfile:$bp_location.*$gdb_prompt $" {
+	pass "disabled breakpoint 1.2"
+    }
+    -re "1\.2.* y .* at .*$hdrfile:$bp_location.*$gdb_prompt $" {
+	# When inferior is restarted, breakpoint locations will be updated.
+	# On uclinux, it is not guaranteed that new inferior is located the
+	# same address as previous one, so status/state of breakpoint location
+	# will loose.  The heuristic of GDB should be improved.
+	setup_kfail gdb/12924 "*-*-uclinux*"
+	fail "disabled breakpoint 1.2"
+    }    
+}
 
 # Make sure we can set a breakpoint on a source statement that spans
 # multiple lines.

      reply	other threads:[~2011-06-23 14:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16  6:17 Yao Qi
2011-06-22 15:38 ` Pedro Alves
2011-06-23  9:21   ` Yao Qi
2011-06-23 10:28     ` Pedro Alves
2011-06-23 13:40       ` Yao Qi
2011-06-23 14:00         ` Pedro Alves
2011-06-23 10:37     ` Pedro Alves
2011-06-23 14:41       ` Yao Qi [this message]

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=4E035078.5070205@codesourcery.com \
    --to=yao@codesourcery.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