From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 780683944822; Mon, 16 Nov 2020 19:35:30 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 780683944822
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/26880] hex instead of filename printed in error message
Date: Mon, 16 Nov 2020 19:35:30 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: gdb
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tromey at sourceware dot org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-26880-4717-k28AE2qyyg@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-26880-4717@http.sourceware.org/bugzilla/>
References: <bug-26880-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gdb-prs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb-prs mailing list <gdb-prs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-prs/>
List-Help: <mailto:gdb-prs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Nov 2020 19:35:30 -0000

https://sourceware.org/bugzilla/show_bug.cgi?id=3D26880

--- Comment #6 from Tom Tromey <tromey at sourceware dot org> ---
(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.

IMO the current situation, with different printf styles in
a single code base, is bad and is going to cause problems
again unless we change it at the root.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=