Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Christophe LYON <christophe.lyon@st.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] obvious pattern fix in gdb.base/step-line.exp
Date: Fri, 27 Mar 2009 14:05:00 -0000	[thread overview]
Message-ID: <49CCDB3D.5010302@st.com> (raw)

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

Hello,

I propose the attached small patch to allow printing the full path 
before 'step-line.c'.

Christophe.

[-- Attachment #2: gdb.step-line.changelog --]
[-- Type: text/plain, Size: 148 bytes --]

2009-03-27  Christophe Lyon  <christophe.lyon@st.com>

	testsuite/
	* gdb.base/step-line.exp: Fix pattern to allow full path before
	"step-line.c".

[-- Attachment #3: gdb.step-line.patch --]
[-- Type: text/plain, Size: 546 bytes --]

Index: gdb/testsuite/gdb.base/step-line.exp
===================================================================
--- gdb/testsuite/gdb.base/step-line.exp	(revision 308)
+++ gdb/testsuite/gdb.base/step-line.exp	(working copy)
@@ -46,7 +46,7 @@ if ![runto_main] then {
    return 0
 }
 
-gdb_test "break f1" ".*Breakpoint 2 at .* file step-line.c.*" "break f1"
+gdb_test "break f1" ".*Breakpoint 2 at .* file .*$srcfile.*" "break f1"
 gdb_test "continue" \
          "Continuing.*Breakpoint 2, f1 \\(i=4\\).*dummy \\(1, i\\);" \
 	 "continue to f1"

             reply	other threads:[~2009-03-27 13:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 14:05 Christophe LYON [this message]
2009-03-27 18:53 ` Joel Brobecker
2009-03-30 13:51   ` Christophe LYON
2009-03-30 18:23     ` Joel Brobecker
2009-03-31 15:25       ` Christophe LYON
2009-04-01 18:32         ` Joel Brobecker
2009-04-02  8:52           ` Christophe LYON
2009-04-17 17:07             ` Christophe LYON
2009-04-17 17:30               ` Daniel Jacobowitz

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=49CCDB3D.5010302@st.com \
    --to=christophe.lyon@st.com \
    --cc=gdb-patches@sources.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