From: Eli Zaretskii <eliz@gnu.org>
To: Guinevere Larsen <blarsen@redhat.com>
Cc: gdb-patches@sourceware.org, simark@simark.ca
Subject: Re: [PATCH v2] gdb: Change "list ." command's error when no debuginfo is available
Date: Thu, 18 Apr 2024 08:10:29 +0300 [thread overview]
Message-ID: <86sezjfe7u.fsf@gnu.org> (raw)
In-Reply-To: <9f1813c5-e74b-4f46-9dde-cefcee757a6d@redhat.com> (message from Guinevere Larsen on Wed, 17 Apr 2024 16:57:32 -0300)
> Date: Wed, 17 Apr 2024 16:57:32 -0300
> Cc: gdb-patches@sourceware.org, simark@simark.ca
> From: Guinevere Larsen <blarsen@redhat.com>
>
> On 4/17/24 16:26, Eli Zaretskii wrote:
> >>>>
> >>>> (gdb) list .
> >>>> No debug information available to print source lines at current PC (0x55555555511d).
> >>>> or
> >>>> (gdb) list .
> >>>> No debug information available to print source lines at default location.
> >>>>
> >>>> The difference now is if the inferior has started already, which is
> >>>> controlled by the user and may be useful.
> >>> How about this text instead:
> >>>
> >>> Insufficient debug info for showing source lines at current PC (0x55555555511d).
> >>>
> >> You mean this change only for the error when the inferior has already
> >> started, or to the prefix of both errors?
> >>
> >> Seeing as the errors are for the same root cause, I'd like to keep the
> >> prefix the same.
> > I'm afraid I don't understand what is the "prefix" in this case.
> >
> Sorry, I meant the start of the sentence. I wasn't sure if you were
> suggesting the errors should be
>
> Insufficient debug info for showing source lines at current PC
> (0x55555555511d).
> No debug information available to print source lines at default
> location.
>
> Or if you meant that they should both be changed to start with
> "insufficient debug info (...)".
I meant to make both begin with "Insufficient debug info", yes.
> I think I prefer this second option,
So we agree.
prev parent reply other threads:[~2024-04-18 5:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 20:00 Guinevere Larsen
2024-04-17 11:58 ` Eli Zaretskii
2024-04-17 19:20 ` Guinevere Larsen
2024-04-17 19:26 ` Eli Zaretskii
2024-04-17 19:57 ` Guinevere Larsen
2024-04-18 5:10 ` Eli Zaretskii [this message]
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=86sezjfe7u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).