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] Fails in gdb.threads/watchthreads-reorder.expwhen run it in non-stop + async


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

Yao Qi <qiyao at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #5 from Yao Qi <qiyao at gcc dot gnu.org> 2012-03-16 13:34:01 UTC ---
(In reply to comment #3)
> > Yes, that is what I really want.  I ported your patch to CVS trunk, and run
> > test suite,
> 
> No it's not what you want.  :-)
> 
> That patch implements *all-stop* on top of non-stop.  There should be no user
> visible change compared to an unpatched gdb, *when you run in all-stop*.
> 

I see.  That makes sense to me.

> Running an all-stop test with "set non-stop 1" tends to only show red herrings,
> as it changes _user-visible behavior and output_.
> 
> non-stop enables a collection of secondary modes: async, and
> displaced-stepping, so test those individually with an unpatched gdb:
> 
>   set GDBFLAGS "-ex \"set target-async on\""
> 
> and:
> 
>   set GDBFLAGS "-ex \"set displaced-stepping on\""

Re-run this test case with asyn on and displaced-stepping on respectively.  No
fails.  Close this one as it is invalid.

-- 
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]