public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/26880] hex instead of filename printed in error message
Date: Tue, 24 Aug 2021 06:15:14 +0000 [thread overview]
Message-ID: <bug-26880-4717-dH4UEwlZhd@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26880-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26880
--- Comment #14 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom Tromey from comment #13)
> (In reply to Tom Tromey from comment #6)
> > (In reply to philippe.waroquiers from comment #5)
> >
> > > Wondering what it would mean to support styled strings in error.
> >
> > The main difficulty is that when the message is constructed,
> > we don't know if it will be printed to a stream that allows
> > styling. However, we do have the machinery needed to strip
> > the styling when printing, so maybe that would be an option.
>
> I think the best approach would be to do this, and to reopen
> this PR as a feature request to implement this idea.
I think it's better to have a spinoff PR, and keep this PR closed:
- it makes sure the PR only refers to the "hex instead of filename" problem.
- it gives clarity about when the problem was fixed.
Filed spinoff PR28259 - "[gdb] Support %ps in error function".
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-08-24 6:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 9:51 [Bug gdb/26880] New: " vries at gcc dot gnu.org
2020-11-14 9:58 ` [Bug gdb/26880] " vries at gcc dot gnu.org
2020-11-14 10:22 ` vries at gcc dot gnu.org
2020-11-14 10:30 ` vries at gcc dot gnu.org
2020-11-14 10:35 ` vries at gcc dot gnu.org
2020-11-14 11:00 ` philippe.waroquiers at skynet dot be
2020-11-16 19:35 ` tromey at sourceware dot org
2021-08-17 23:19 ` kuba at kadziolka dot net
2021-08-18 7:14 ` vries at gcc dot gnu.org
2021-08-23 10:08 ` cvs-commit at gcc dot gnu.org
2021-08-23 19:08 ` cvs-commit at gcc dot gnu.org
2021-08-23 19:10 ` vries at gcc dot gnu.org
2021-08-23 19:10 ` vries at gcc dot gnu.org
2021-08-23 20:19 ` tromey at sourceware dot org
2021-08-24 6:15 ` vries at gcc dot gnu.org [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=bug-26880-4717-dH4UEwlZhd@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).