Re: [cdt-dev] target unexpectedly stops on a SIGINT while setting break

[Doug Schaefer <cdtdoug@xxxxxxxxx>]

On Thu, Mar 4, 2010 at 12:47 PM, John Cortell <rat042@xxxxxxxxxxxxx> wrote:

At 10:49 AM 3/4/2010, Daniel Jacobowitz wrote:

On Thu, Mar 04, 2010 at 11:15:40AM -0500, Marc Khouzam wrote:
> We only use async mode when using non-stop.  I did consider making the switch
> but two things stopped me:
>
> 1- lots of regression testing since everything would be using asych GDB mode
> instead of the traditional synch mode.
> 2- We still need to support older GDBs (we support 6.6 and up), so we'd still
> need to keep the code for the sync mode.
>
> If it is a big enough problem, we could give it a try for GDB 7.0 and fix the problem
> there only, but I'm not sure it is worth the effort.

Only my two cents, but I don't like thinking about the situation this
way.  If we want to give users the best experience, we need to be
aggressive about taking advantage of newer features in GDB.

I think that's an over simplification of this particular situation. Taking advantage of a new feature is one thing. Altering something as fundamental as how the debugger interacts with gdb (for all commands) in order to address one particular issue...that's another story. Now, I think the issue in this case is serious enough to warrant considering the option, but it makes sense to me that we would be cautious, even hesitant. 

I'm of the opinion this is very serious. Bizarre behavior on interrupt is one of the main reasons I consider using EDC for Windows instead of gdb. If gdb 7, the version we can recommend for MinGW users and what will be in Wascana 1.0, has a solution we should go for it. And I don't see this as a major change. The only thing affected should be gdb startup and the interrupt code. We don't need to introduce any additional async functionality, at least not right away.