Vladimir Prus wrote:
> FWIW, you don't say what function in mi-support.exp is changed,
> and it would be better if your patch was generated with -u (unified diff,
> 3 lines of context) -- the current one has no context at all, so I
> can only guess which function that is.

Please find attached new diffs.


> 
> Speaking of the problem itself -- in PR2424 you say:
> 
>         When inferior stops at temporary breakpoint, message is:
>         *stopped,thread-id="0",.......
>         without mentioning "reason=breakpoint-hit"
>         This causes issues for multithreaded programs.
> 
> What issues does it cause for MT programs?

When inferior hits a temporary breakpoint, due to breakpoint removal the reason 
for stop is "lost in translation". This leaves user guessing what the reason for 
stop was. This  is applicable to both single and multi threaded inferiors, but 
gets more annoying when multiple threads exist since then client program (in my 
case IDE - CDT) can not figure out which thread caused the stop in addition to 
not knowing the reason (I am not working on CDT but I was explained that missing 
"reason" is to blame, and after the patch I proposed I was told things now work 
as expected).


@Nick: I think the breakpoint should be reported. The fact that it is temporary 
doesn't make it much different than a regular breakpoint... but maybe I'm 
missing something.