[Bug mi/34501] gdb responds with corrupt output on trying to inserting a breakpoint

https://sourceware.org/bugzilla/show_bug.cgi?id=34501

--- Comment #10 from Jarmo Tiitto <jarmo.tiitto at gmail dot com> ---
(In reply to Tom de Vries from comment #7)
> I managed to reproduce this, with current gdb built at O0, and:
> ...
> $ gdb \
>     -q \
>     -ex 'set charset UTF-8' \
>     -ex 'interpreter-exec mi2 "-break-insert -f foo' \
>     -ex quit
> ...
> 
> Using "set style emoji off" fixes this for me.
> 
> So, the prefix you're seeing is the error-prefix:
> ...
> (gdb) show style error-prefix
> Error prefix is "❌️ ".
> ...
> 
> Whether there's a bug in gdb or not, I'm not sure.
> 
> But if so, it's simply a usability bug of the type "don't use emojis in MI"
> or something like that.

Why are emojis suddenly by default enabled for mi2, which never had such
before?

> The output is UTF-8 encoded Unicode.  The only issue is that the leading byte is printed directly instead of escaped.

Probably why the KDevelop couldn't show the output and I was here thinking
there was a serious bug in GDB, when it's just (a bit brokenly) printing emojis
now. :D

Anyway, I'm going to add "set style emoji off" to kdevgdb's startup commands so
the emojis don't pollute the already verbose output. I can report back when the
leading byte issue is fixed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.