This is the mail archive of the gdb-patches@sources.redhat.com 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: RFC: Always use at least schedlock_step for software single step targets


On Fri, Jun 06, 2003 at 05:36:45PM -0400, Andrew Cagney wrote:
> 
> >It effectively forces schedlock_step for SSS targets
> >(but I guess you knew that).  People appear to be very
> >diverse in their opinion about whether schedlock is the
> >"right" behavior or the "wrong" one.  You might not see
> >the behavior that you're trying to debug, if you're only
> >stepping one thread.
> 
> There are targets for which sched lock almost meaningless, but then, 
> hopefully those targets also support hardware single step.
> 
> The change looks to be the best option.

I think I'm going to revisit an event scheduler in gdbserver to fix the
livelock, before I commit this.  Since I'd rather schedlock worked on
mips-linux.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


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