Re: [PATCH 0/1] Integrate GNU poke in GDB

[Tom Tromey <tom@tromey.com>]

>>>>> "Simon" == Simon Marchi via Gdb-patches <gdb-patches@sourceware.org> writes:

Simon> I don't find this super clear, as we could always see it both
Simon> ways.

One my pet peeves about autoconf is that the --with/--enable distinction
is too subtle to ever remember or care about.  Like, what would it mean
if a program had both --enable-x and --with-x?  I think it would be
better to just declare them as synonyms.

Simon> From target_read_raw_memory's doc:

Simon> /* Like target_read_memory, but specify explicitly that this is a read
Simon>    from the target's raw memory.  That is, this read bypasses the
Simon>    dcache, breakpoint shadowing, etc.  */

Simon> So, it bypasses a cache in GDB (not sure why that's important).

gdb tries to cache some memory to avoid excess requests to the remote.
This matters if you have a slow connection.

>> - How can I demangle C++ identifiers?  And how can I detect when
>> a given type is a C++ one that needs demangling?

Simon> I think that we usually rely on the language of the compilation unit, as
Simon> given by DWARF, to know that a symbol has a C++ mangled name and needs
Simon> demangling.

I can't remember if I mentioned this elsewhere, but type names aren't
normally mangled.  Symbol names for variables or functions can be, but
gdb already does the demangling if you use the correct accessor.

Tom