This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] gcore registers storing fix




Daniel Jacobowitz wrote:
On Mon, Nov 09, 2009 at 03:17:36PM -0300, Daniel Gutson wrote:
The problem shows up when "in ??" appears. I think that the current
thread will never be shown in that way unless the test does fail.
That being said, I think that I could add the regex for the "*" in
order to looking into the current thread only.

How is that different from the two following tests in gcore-thread.exp?

# One thread in the corefile should be in the "thread2" function.

gdb_test "info threads" ".* thread2 .*" \
        "a corefile thread is executing thread2"

# The thread2 thread should be marked as the current thread.

gdb_test "info threads" ".*${nl}\\* ${horiz} thread2 .*" \
        "thread2 is current thread in corefile"


Because none of them checks that the text "in ??" does *not* show up


--
Daniel Gutson
CodeSourcery
www.codesourcery.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]