public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/28948] Enabling/disabling logging over an interpreter switch can crash gdb Date: Wed, 10 Aug 2022 19:07:12 +0000 [thread overview] Message-ID: <bug-28948-4717-Zo5bXKPhbs@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28948-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28948 Tom Tromey <tromey at sourceware dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot org --- Comment #1 from Tom Tromey <tromey at sourceware dot org> --- I've been looking at logging oddities a bit today and I think maybe this entire area could be simplified. The basic idea is to separate gdb_stdout (and stderr and stdlog) from the raw, underlying stdout/log. Most code uses gdb_stdout, and this would still be managed by the particular interpreter. This way MI can wrap the output in the syntax it uses. However, the new idea is to have a global raw_stdout and raw_stdlib. The interp-provided streams would be required to redirect to these dynamically. The "set logging" commands would affect just the raw_ globals. This way, switching between interpreters would be completely fine. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-08-10 19:07 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-07 21:38 [Bug gdb/28948] New: " aburgess at redhat dot com 2022-08-10 19:07 ` tromey at sourceware dot org [this message] 2022-08-11 13:05 ` [Bug gdb/28948] " tromey at sourceware dot org 2022-08-12 17:23 ` tromey at sourceware dot org 2022-08-12 20:02 ` 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-28948-4717-Zo5bXKPhbs@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: linkBe 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).