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: [cancel] [patch] More suggestive error_is_running message


> The whole point of my patch was not notify about the _wait_, not about
> the _interrupt_, as this is what one cannot easily catch when
> debugging a testcase after converting it full-stop -> non-stop.  If
> you try to reproduce the problem by hand it works.  OK, I admit I am
> too stupid to write GDB testcases.

I missed a bit the context leading to the improvement you were
suggesting, but it was not my intention to say that you are "too
stupid to [...]" at all. This sounds like a harsh criticism of
yourself - perhaps a quirk of English not being our native language
for both of us.

In any case, as I said, I don't have a strong opinion. I know that
we want to both have concise error messages, while at the same time
making GDB more explanatory on some confusing or tricky  situations.
This is a real conundrum.

-- 
Joel


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