Re: [RFA/doco] Document task-specific breakpoints

Joel Brobecker
2009-03-27T16:11:08Z

> But in fact, it isn't executing some code, it's stopped at a
> breakpoint, isn't it? If it is executing code, what code is that?
[...]
> If I were the user looking at the "Running" status, I'd certainly
> think that something is dead wrong with this task-specific breakpoint.

It's been a naming convention that we have been using for 10+ years.
So far, we have had no report about this, either customer or internal.
Customer support is at the heart of our business, so we are fairly
pro-active at encouraging our customers in sending reports.

It does NOT mean that you're wrong, but I do disagree with you on this
one and I definitely feel like being dragged in a bikeshed discussion.
So, unless others also think that this is confusing, I'm not going to
change GDB, but I'll agree to change the documentation instead.

The problem is that I don't understand what it is that is so confusing
to you. I understand that the task is not executing code precisely
at the moment where the state was printed, but it was just before
the program was stopped, and it will when the program is resumed.

What I propose, at this stage, is that you look at the documentation
in the GDB manual, and update the description of the "Running" state
to provide whatever piece of information you think needs to be added.
I can do that for you if you tell me what you want to me add.

--
Joel