Hello,
> Thanks for fixing this!
>
> This is OK, but please double-check the patch/commit, since it
> seems to include the same hunk twice. Kind of looks like
> the fix diff made it to the commit log?
Oops yes, it's because I use "git commit -v" and managed to include
that
diff in the commit message by mistake.
Pushed with that fixed.
Just a quick message to let you know that I cherry-picked the patch and
pushed it to gdb-8.2-branch. I think we wanted this to be fixed there,
right? And the patch looked sufficiently obvious to me that I went
ahead.