Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Guinevere Larsen via Gdb <gdb@sourceware.org>
To: Eli Zaretskii <eliz@gnu.org>, Phi Debian <phi.debian@gmail.com>
Cc: psmith@gnu.org, gdb@sourceware.org
Subject: Re: Improve GDB's first user experience by reducing "print_gdb_version" output
Date: Wed, 28 May 2025 09:24:00 -0300	[thread overview]
Message-ID: <d9ae9cf1-34f3-4a59-8e0d-7ee526cb04c4@redhat.com> (raw)
In-Reply-To: <86ikllvsfb.fsf@gnu.org>

On 5/28/25 9:19 AM, Eli Zaretskii wrote:
>> Date: Wed, 28 May 2025 09:33:09 +0200
>> Cc: Guinevere Larsen <guinevere@redhat.com>,
>>   "gdb@sourceware.org" <gdb@sourceware.org>
>> From: Phi Debian via Gdb <gdb@sourceware.org>
>>
>> FWIW lldb produce nothing
>>
>> $ lldb ./hw
>> (lldb) target create "./hw"
>> Current executable set to '/tmp/hw' (x86_64).
>> (lldb)
>>
>>
>> One could argue LLVM series is not GNU yet GCC don't produce nothing either
>> (even with -v)
> Unlike GDB, GCC is not an interactive program, so it produces this
> information in the output of "gcc --version" and "gcc --help".
>
>> The proposed minimal greeting is nice, or can be push further with no
>> greeting at all (like lldb) assuming gdb --help or man gdb would be the
>> starting point leading to apropos...
> That'd be going too far, IMO.
>
Using -q or --quiet already does this, so we already allow this for 
users who would like a completely silent start (I personally have `alias 
gdb='gdb -q'` in my bashrc).

I agree that having this be the default behavior is too far. If 
anything, I'd like to tutorialize GDB a little bit more, and completely 
hiding the helpful parts of the initial message is the opposite of what 
I hope to accomplish.

-- 
Cheers,
Guinevere Larsen
She/Her/Hers


  reply	other threads:[~2025-05-28 12:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-27 20:43 Guinevere Larsen via Gdb
2025-05-27 21:38 ` Paul Smith via Gdb
2025-05-28  7:33   ` Phi Debian via Gdb
2025-05-28 12:19     ` Eli Zaretskii via Gdb
2025-05-28 12:24       ` Guinevere Larsen via Gdb [this message]
2025-05-28 13:04         ` Paul Smith via Gdb
     [not found]       ` <CAJOr74gc9zeHQGST3eufT9zYJEsdEkO4m4xgxhQyQNE3kpSUNw@mail.gmail.com>
2025-05-29  9:16         ` Eli Zaretskii via Gdb
2025-05-28  7:44   ` Mark Wielaard
2025-05-28 12:30     ` Guinevere Larsen via Gdb
2025-05-30 11:22     ` Florian Weimer via Gdb
2025-05-30 20:39       ` Mark Wielaard
2025-05-28 11:47   ` Eli Zaretskii via Gdb
2025-05-28 11:39 ` Eli Zaretskii via Gdb
2025-05-28 12:15   ` Guinevere Larsen via Gdb

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d9ae9cf1-34f3-4a59-8e0d-7ee526cb04c4@redhat.com \
    --to=gdb@sourceware.org \
    --cc=eliz@gnu.org \
    --cc=guinevere@redhat.com \
    --cc=phi.debian@gmail.com \
    --cc=psmith@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox