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] Don't switch to the event thread early in non-stop mode.

From: Pedro Alves <palves at redhat dot com>
To: Yao Qi <yao at codesourcery dot com>
Cc: gdb-patches at sourceware dot org
Date: Wed, 13 Jun 2012 09:52:34 +0100
Subject: Re: [PATCH] Don't switch to the event thread early in non-stop mode.
References: <20120612184440.29776.25769.stgit@brno.lan> <4FD7E784.1080508@codesourcery.com>

On 06/13/2012 02:06 AM, Yao Qi wrote:

> On 06/13/2012 02:44 AM, Pedro Alves wrote:
>>      case TARGET_WAITKIND_SPURIOUS:
>>        if (debug_infrun)
>>          fprintf_unfiltered (gdb_stdlog, "infrun: TARGET_WAITKIND_SPURIOUS\n");
>> +      if (!ptid_equal (ecs->ptid, inferior_ptid)
>> +	  && !ptid_equal (ecs->ptid, minus_one_ptid))
>> +	context_switch (ecs->ptid);
> 
> Is there any reason to check minus_one_ptid?


Yes, linux-thread-db.c returns TARGET_WAITKIND_SPURIOUS with minus_one_ptid.
Originated here:

 http://sourceware.org/ml/gdb-patches/2004-06/msg00073.html

-- 
Pedro Alves

References:
- [PATCH] Don't switch to the event thread early in non-stop mode.
  - From: Pedro Alves
- Re: [PATCH] Don't switch to the event thread early in non-stop mode.
  - From: Yao Qi

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