This is the mail archive of the gdb-prs@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]

[Bug testsuite/13859] `set non-stop 1' triggers some fails ingdb.threads/watchthreads-reorder.exp


http://sourceware.org/bugzilla/show_bug.cgi?id=13859

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |palves at redhat dot com

--- Comment #1 from Pedro Alves <palves at redhat dot com> 2012-03-16 10:22:36 UTC ---
> Haven't analyzed these fails carefully yet, but looks like they are caused by
> the test case that is unable to parse/match output after displaced stepping is
> on.  Open this PR against component `testsuite'.

Weird, just displaced stepping ("set displaced-stepping on") should not affect
the output.  non-stop+async has different behavior and output by design.  Is
that what you're really trying?  These tests have been written for all-stop. 
Why would you be running them with "set non-stop 1", and expecting them to
work?

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


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