[Bug gdb/31152] Formalise unintened functionality in version 9.1

["chris_douglas_email at yahoo dot com" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #8 from stephen douglas <chris_douglas_email at yahoo dot com> ---
I have tried to create a “simple patch” to fix the warning in comment 3 (as
requested in comment 6). However, there appears to be 3 variants of iconv, the
iconv built from the source of glibc (comments refer to this as gconv), the
iconv provided by libiconv, and use of libintl. I use gconv. I believe someone
with a knowledge of iconv in gdb would stand a better chance. To reproduce the
warning, make the equivalent of
/usr/lib/x86_64-linux-gnu/gconv/gconv-modules.cache inaccessible. This is not
of any particular concern to me as the fallback processing does everything I
want.

I raised this bug because I believed something had been lost between versions
9.2 and 14.1. I wish to use gdb as a “black box” because it has a deserved
reputation for being “bullet proof”. For it to survive under the initial
conditions, it would need to be “anti-tank missile proof” because the kernels I
am trying to use, in general, reset the box on any error. You have “protection”
(or should I say fixes) for conditions more obscure than the one that caused me
grief. Personally, my current “grey box” knowledge will allow me to have
somewhere to look if I can determine that not getting to the initial
announcement is due to a segment trap, so I no longer “need” a fix.

There are now 2 issues on this bug, I leave it to whoever runs the system if
either are considered valid, and process this bug accordingly.

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