public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/7233] Send output to gdb_stdout et.al.
Date: Wed, 29 Dec 2021 18:02:49 +0000 [thread overview]
Message-ID: <bug-7233-4717-WDyxy9irO2@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-7233-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=7233
--- Comment #7 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=7fea6c34a1bcf11757c9d76c9d23ca5372d56501
commit 7fea6c34a1bcf11757c9d76c9d23ca5372d56501
Author: Tom Tromey <tom@tromey.com>
Date: Fri Dec 24 22:19:10 2021 -0700
Use debug_prefixed_printf_cond_nofunc in microblaze.c
This changes microblaze.c to use the standard logging macro. As a
side effect, logs will now go to gdb_stdlog. This is part of PR gdb/7233.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=7233
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-12-29 18:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-7233-4717@http.sourceware.org/bugzilla/>
2014-09-16 19:30 ` sergiodj at redhat dot com
2014-09-16 19:41 ` cvs-commit at gcc dot gnu.org
2021-12-29 17:47 ` cvs-commit at gcc dot gnu.org
2021-12-29 17:47 ` cvs-commit at gcc dot gnu.org
2021-12-29 17:47 ` cvs-commit at gcc dot gnu.org
2021-12-29 18:02 ` cvs-commit at gcc dot gnu.org
2021-12-29 18:02 ` cvs-commit at gcc dot gnu.org [this message]
2021-12-29 18:02 ` cvs-commit at gcc dot gnu.org
2021-12-29 18:02 ` cvs-commit at gcc dot gnu.org
2021-12-29 18:03 ` cvs-commit at gcc dot gnu.org
2021-12-29 18:03 ` cvs-commit at gcc dot gnu.org
2021-12-29 18:03 ` cvs-commit at gcc dot gnu.org
2022-04-08 0:11 ` tromey at sourceware dot org
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-7233-4717-WDyxy9irO2@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).