[PATCH] Remove unused str_backtrace_unavailable variable

[PATCH] Remove unused str_backtrace_unavailable variable

[Luis Machado]

The str_backtrace_unavailable variable is initialized but never
used anywhere in the codebase.
---
 gdb/bt-utils.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/gdb/bt-utils.c b/gdb/bt-utils.c
index 7fc8d04f306..21a291c3df3 100644
--- a/gdb/bt-utils.c
+++ b/gdb/bt-utils.c
@@ -146,7 +146,6 @@ gdb_internal_backtrace_1 ()
 #endif
 
 static const char *str_backtrace = "----- Backtrace -----\n";
-static const char *str_backtrace_unavailable = "Backtrace unavailable\n";
 
 #endif /* GDB_PRINT_INTERNAL_BACKTRACE */
 
@@ -157,7 +156,6 @@ gdb_internal_backtrace_init_str ()
 {
 #ifdef GDB_PRINT_INTERNAL_BACKTRACE
   str_backtrace = _("----- Backtrace -----\n");
-  str_backtrace_unavailable = _("Backtrace unavailable\n");
 #endif
 }
 
-- 
2.34.1

Re: [PATCH] Remove unused str_backtrace_unavailable variable

[Tom Tromey]

>>>>> "Luis" == Luis Machado <luis.machado@amd.com> writes:

Luis> The str_backtrace_unavailable variable is initialized but never
Luis> used anywhere in the codebase.

Thanks.

Approved-By: Tom Tromey <tom@tromey.com>

Tom

Re: [PATCH] Remove unused str_backtrace_unavailable variable

[Simon Marchi]

On 5/1/26 3:31 AM, Luis Machado wrote:
> The str_backtrace_unavailable variable is initialized but never
> used anywhere in the codebase.
> ---
>  gdb/bt-utils.c | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/gdb/bt-utils.c b/gdb/bt-utils.c
> index 7fc8d04f306..21a291c3df3 100644
> --- a/gdb/bt-utils.c
> +++ b/gdb/bt-utils.c
> @@ -146,7 +146,6 @@ gdb_internal_backtrace_1 ()
>  #endif
>  
>  static const char *str_backtrace = "----- Backtrace -----\n";
> -static const char *str_backtrace_unavailable = "Backtrace unavailable\n";
>  
>  #endif /* GDB_PRINT_INTERNAL_BACKTRACE */
>  
> @@ -157,7 +156,6 @@ gdb_internal_backtrace_init_str ()
>  {
>  #ifdef GDB_PRINT_INTERNAL_BACKTRACE
>    str_backtrace = _("----- Backtrace -----\n");
> -  str_backtrace_unavailable = _("Backtrace unavailable\n");
>  #endif
>  }

Seems quite obvious to me, but I would wait for Andrew to confirm that
this wasn't meant to be used somewhere.  For instance, in the
libbacktrace_error function.  But I think the message there is clear, so
I'd be fine with just deleting the variable.

Simon

Re: [PATCH] Remove unused str_backtrace_unavailable variable

[Luis]

On 01/05/2026 15:17, Simon Marchi wrote:
> On 5/1/26 3:31 AM, Luis Machado wrote:
>> The str_backtrace_unavailable variable is initialized but never
>> used anywhere in the codebase.
>> ---
>>   gdb/bt-utils.c | 2 --
>>   1 file changed, 2 deletions(-)
>>
>> diff --git a/gdb/bt-utils.c b/gdb/bt-utils.c
>> index 7fc8d04f306..21a291c3df3 100644
>> --- a/gdb/bt-utils.c
>> +++ b/gdb/bt-utils.c
>> @@ -146,7 +146,6 @@ gdb_internal_backtrace_1 ()
>>   #endif
>>   
>>   static const char *str_backtrace = "----- Backtrace -----\n";
>> -static const char *str_backtrace_unavailable = "Backtrace unavailable\n";
>>   
>>   #endif /* GDB_PRINT_INTERNAL_BACKTRACE */
>>   
>> @@ -157,7 +156,6 @@ gdb_internal_backtrace_init_str ()
>>   {
>>   #ifdef GDB_PRINT_INTERNAL_BACKTRACE
>>     str_backtrace = _("----- Backtrace -----\n");
>> -  str_backtrace_unavailable = _("Backtrace unavailable\n");
>>   #endif
>>   }
> 
> Seems quite obvious to me, but I would wait for Andrew to confirm that
> this wasn't meant to be used somewhere.  For instance, in the
> libbacktrace_error function.  But I think the message there is clear, so
> I'd be fine with just deleting the variable.

Sorry, I just pushed this. But we can still wait for Andrew to chime in 
and tell us otherwise.

Re: [PATCH] Remove unused str_backtrace_unavailable variable

[Tom Tromey]

>>>>> "Simon" == Simon Marchi <simark@simark.ca> writes:

Simon> Seems quite obvious to me, but I would wait for Andrew to confirm that
Simon> this wasn't meant to be used somewhere.  For instance, in the
Simon> libbacktrace_error function.  But I think the message there is clear, so
Simon> I'd be fine with just deleting the variable.

I considered this before approving but my view is that if it is needed,
it is trivial to revert a deletion like this.

I'd generally consider the removal of an unused object to be obvious,
with the caveats:

1. If it looks like maybe it *ought* to be used, then send an RFA
   instead;
2. Be sure to check Insight as it uses a few things that are otherwise
   unused.

Tom

Re: [PATCH] Remove unused str_backtrace_unavailable variable

[Machado, Luis]

Thanks for the heads up on Insight. For context, this came up when using llvm.

It got grumpy about the unused-but-initialized value.

________________________________________
From: Tom Tromey <tom@tromey.com>
Sent: Friday, 1 May 2026 16:50
To: Simon Marchi
Cc: Machado, Luis; gdb-patches@sourceware.org
Subject: Re: [PATCH] Remove unused str_backtrace_unavailable variable

Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.


>>>>> "Simon" == Simon Marchi <simark@simark.ca> writes:

Simon> Seems quite obvious to me, but I would wait for Andrew to confirm that
Simon> this wasn't meant to be used somewhere.  For instance, in the
Simon> libbacktrace_error function.  But I think the message there is clear, so
Simon> I'd be fine with just deleting the variable.

I considered this before approving but my view is that if it is needed,
it is trivial to revert a deletion like this.

I'd generally consider the removal of an unused object to be obvious,
with the caveats:

1. If it looks like maybe it *ought* to be used, then send an RFA
   instead;
2. Be sure to check Insight as it uses a few things that are otherwise
   unused.

Tom