I don't understand the problem that this is trying to solve, and the
paper isn't describing it either. As an example, when debugging code,
I have never wanted to ask the question of "what is the address of the
destructor", or "how many virtual functions does this class have".

On Wed, Nov 27, 2024 at 2:11 PM Frederick Virchanza Gotham via
Std-Proposals <std-proposals_at_[hidden]> wrote:
>
> Here's a paper describing the beginnings of a new header file called
> <debug> which would standardise debugging across all C++ compilers:
>
> http://www.virjacode.com/papers/stddebug.htm
>
> So far it has stuff for vtables, constructors, destructors. I can
> think of other stuff to put in it like:
>
> * is_immediate_jump : Checks the machine code pointed to by a function
> pointer to see if the first instruction is a jump, and if so, returns
> the address of the jump destination.
>
> * size_of_function : Returns the size in bytes of the machine code of
> a function (not sure if the object file containing the function's
> machine code always has the function's total size in bytes)
>
> * is_executable_memory : Returns true if code can be executed at the
> specified address
>
> * is_readonly_memory : Return true if the specified span<byte> points
> to memory which is either partially or fully readonly.
> --
> Std-Proposals mailing list
> Std-Proposals_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals