public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Support styling on native MS-Windows console
Date: Sat, 09 Mar 2019 07:02:00 -0000 [thread overview]
Message-ID: <e4adb93903d4ae0b7ab2b5004364e50627df95f7@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT e4adb93903d4ae0b7ab2b5004364e50627df95f7 ***
Author: Eli Zaretskii <eliz@gnu.org>
Branch: master
Commit: e4adb93903d4ae0b7ab2b5004364e50627df95f7
Support styling on native MS-Windows console
gdb/ChangeLog:
2019-03-08 Eli Zaretskii <eliz@gnu.org>
PR/24315
* utils.c (can_emit_style_escape) [_WIN32]: Don't disable styling
on MS-Windows if $TERM is not defined.
* cli/cli-style.c: Set cli_styling to 1 in the MinGW build.
* posix-hdep.c (gdb_console_fputs):
* mingw-hdep.c (rgb_to_16colors, gdb_console_fputs): New
functions.
* ui-file.h (gdb_console_fputs): Add prototype.
* ui-file.c (stdio_file::puts): Call gdb_console_fputs, and fall
back to fputs only if the former returns zero.
next reply other threads:[~2019-03-09 7:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-09 7:02 sergiodj+buildbot [this message]
2019-03-09 7:02 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2019-03-09 7:54 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2019-03-09 8:12 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2019-03-10 12:11 ` Failures on Fedora-i686, " sergiodj+buildbot
2019-03-10 13:04 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2019-03-10 14:56 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2019-03-10 15:18 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2019-03-10 15:29 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2019-03-10 16:21 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2019-03-10 16:26 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
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=e4adb93903d4ae0b7ab2b5004364e50627df95f7@gdb-build \
--to=sergiodj+buildbot@sergiodj.net \
--cc=gdb-testers@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).