From: Denis PILAT <denis.pilat@st.com>
To: Denis PILAT <denis.pilat@st.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [RFA] thread apply commands change selected frame
Date: Thu, 01 Feb 2007 09:49:00 -0000 [thread overview]
Message-ID: <45C1AF6E.9080900@st.com> (raw)
In-Reply-To: <20070131193254.GA7389@nevyn.them.org>
[-- Attachment #1: Type: text/plain, Size: 694 bytes --]
Daniel Jacobowitz wrote:
> On Wed, Jan 31, 2007 at 04:57:50PM +0100, Denis PILAT wrote:
>
>> Your remarks have been taken into account into the attached patch.
>> Are you ok for committing this one plus the previous patch regarding the
>> thread.c ?
>> (Frederic Riss will do that for me)
>>
>
> Yes, that's OK (with a minor fix, below). Let me know if you would
> like write access yourself.
>
Yes thanks.
> Checking for $[specific number] should be avoided, because adding more
> tests earlier in the file will break it. Use \\\$\[0-9]+ instead.
>
>
I prefer that as well, therefore I changed the previous test as well to
keep the same style (see attached file).
--
Denis
[-- Attachment #2: threadapply.exp.patch --]
[-- Type: text/plain, Size: 1525 bytes --]
2007-02-01 Denis Pilat <denis.pilat@st.com>
* gdb.threads/threadapply.exp: check that frame is not changed by
the thread apply all command.
Index: testsuite/gdb.threads/threadapply.exp
===================================================================
--- testsuite/gdb.threads/threadapply.exp (revision 553)
+++ testsuite/gdb.threads/threadapply.exp (working copy)
@@ -67,5 +67,11 @@ gdb_test_multiple "define backthread" "d
# verify that the macro can get past the backtrace error and perform
# subsequent commands.
gdb_test "set backtrace limit 3" ""
-gdb_test "thread apply all backthread" "Thread ..*\\\$1 = 0x14.*Thread ..*\\\$2 = 0x14.*Thread ..*\\\$3 = 0x14.*Thread ..*\\\$4 = 0x14.*Thread ..*\\\$5 = 0x14.*Thread ..*\\\$. = 0x14"
+gdb_test "thread apply all backthread" "Thread ..*\\\$\[0-9]+ = 0x14.*Thread ..*\\\$\[0-9]+ = 0x14.*Thread ..*\\\$\[0-9]+ = 0x14.*Thread ..*\\\$\[0-9]+ = 0x14.*Thread ..*\\\$\[0-9]+ = 0x14.*Thread ..*\\\$\[0-9]+ = 0x14"
+# Go into the thread_function to check that a simple "thread apply"
+# does not change the selected frame.
+gdb_test "step" "thread_function.*" "step to the thread_function"
+gdb_test "up" ".*in main.*" "go up in the stack frame"
+gdb_test "thread apply all print 1" "Thread ..*\\\$\[0-9]+ = 1.*Thread ..*\\\$\[0-9]+ = 1.*Thread ..*\\\$\[0-9]+ = 1.*Thread ..*\\\$\[0-9]+ = 1.*Thread ..*\\\$\[0-9]+ = 1.*Thread ..*\\\$\[0-9]+ = 1" "run a simple print command on all threads"
+gdb_test "down" "#0.*thread_function.*" "go down and check selected frame"
next prev parent reply other threads:[~2007-02-01 9:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 11:24 [RFC] " Denis PILAT
2007-01-21 17:33 ` Daniel Jacobowitz
2007-01-24 10:42 ` Denis PILAT
2007-01-31 8:58 ` Denis PILAT
2007-01-31 14:54 ` Daniel Jacobowitz
2007-01-31 19:30 ` Denis PILAT
2007-01-31 19:33 ` Daniel Jacobowitz
2007-02-01 9:49 ` Denis PILAT [this message]
2007-02-01 14:33 ` [RFA] " Daniel Jacobowitz
2007-02-02 12:40 ` Denis PILAT
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=45C1AF6E.9080900@st.com \
--to=denis.pilat@st.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