Hi Alex,
On 6/21/24 5:11 AM, Alex Bennée wrote:
Gustavo Romero writes:
Currently, it's not possible to have stubs specific to a given target,
even though there are GDB features which are target-specific, like, for
instance, memory tagging.
This commit introduces gdb_extend_qsupported_feature
Richard Henderson writes:
> On 6/16/24 23:28, Gustavo Romero wrote:
>> +static char *extended_qsupported_features;
>> +void gdb_extend_qsupported_features(char *qsupported_features)
>> +{
>> +extended_qsupported_features = qsupported_features;
>> +}
>
> Assert these functions aren't called tw
Gustavo Romero writes:
> Currently, it's not possible to have stubs specific to a given target,
> even though there are GDB features which are target-specific, like, for
> instance, memory tagging.
>
> This commit introduces gdb_extend_qsupported_features,
> gdb_extend_query_table, and gdb_extend
On 6/16/24 23:28, Gustavo Romero wrote:
+static char *extended_qsupported_features;
+void gdb_extend_qsupported_features(char *qsupported_features)
+{
+extended_qsupported_features = qsupported_features;
+}
Assert these functions aren't called twice.
That should be good enough until we need
Currently, it's not possible to have stubs specific to a given target,
even though there are GDB features which are target-specific, like, for
instance, memory tagging.
This commit introduces gdb_extend_qsupported_features,
gdb_extend_query_table, and gdb_extend_set_table functions as interfaces
t
