From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/4] Change how stdlog timestamps are written
Date: Thu, 24 Mar 2022 10:21:46 -0600 [thread overview]
Message-ID: <87tubnuxr9.fsf@tromey.com> (raw)
In-Reply-To: <20211231201901.1567610-1-tom@tromey.com> (Tom Tromey's message of "Fri, 31 Dec 2021 13:18:57 -0700")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> I've been looking at the GDB ui_file and pager system to see if it can
Tom> be made more understandable -- right now it's fairly spaghetti-ish,
Tom> with ui_file calling into functions in util.c, that then dispatch back
Tom> to ui_file. My vision for the endpoint is something along the lines
Tom> of Java's stream writers, where additional functionality is provided
Tom> by just instantiating some new writer to wrap an existing one.
Tom> This series is a step toward that long-term goal. It changes how
Tom> gdb_stdlog timestamps are written, moving this into a new ui_file
Tom> subclass. This avoids a special case (which may in some situations be
Tom> incorrect, see patch #4) in vfprintf_unfiltered.
I'm going to push this soon, probably next week, as it is needed for the
pager-as-ui-file series.
Tom
next prev parent reply other threads:[~2022-03-24 16:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 20:18 Tom Tromey
2021-12-31 20:18 ` [PATCH 1/4] Simplify the CLI set_logging logic Tom Tromey
2021-12-31 20:18 ` [PATCH 2/4] Use unique_ptr in CLI logging code Tom Tromey
2021-12-31 20:19 ` [PATCH 3/4] Add new timestamped_file class Tom Tromey
2021-12-31 20:19 ` [PATCH 4/4] Switch gdb_stdlog to use timestamped_file Tom Tromey
2022-03-24 16:21 ` Tom Tromey [this message]
2022-03-28 20:12 ` [PATCH 0/4] Change how stdlog timestamps are written Tom Tromey
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=87tubnuxr9.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@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).