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+doc] Fix PR threads/19422 - show which thread caused stop


On Thu, 14 Jan 2016 15:08:40 +0100, Pedro Alves wrote:
[...]
> 	* gdb.base/watchpoint-hw-hit-once.exp: Adjust expected output.
[...]
> diff --git a/gdb/testsuite/gdb.base/watchpoint-hw-hit-once.exp b/gdb/testsuite/gdb.base/watchpoint-hw-hit-once.exp
> index 5c1be00..46d5c62 100644
> --- a/gdb/testsuite/gdb.base/watchpoint-hw-hit-once.exp
> +++ b/gdb/testsuite/gdb.base/watchpoint-hw-hit-once.exp
> @@ -31,7 +31,7 @@ gdb_test "rwatch watchee"
>  
>  gdb_breakpoint [gdb_get_line_number "dummy = 2"]
>  
> -gdb_test "continue" "Continuing.\r\nHardware read watchpoint \[0-9\]+: watchee\r\n\r\nValue = 0\r\n.*"
> +gdb_test "continue" "Continuing.\r\n\r\nHardware read watchpoint \[0-9\]+: watchee\r\n\r\nValue = 0\r\n.*"

I haven't seen a comment why such change is necessary.  It probably happens
from some of the changes involved but not sure if it was really required.


Thanks,
Jan


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