From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0C81C3857359; Wed, 10 Aug 2022 19:07:13 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0C81C3857359 From: "tromey at sourceware dot 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 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: cc Message-ID: In-Reply-To: References: 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 List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2022 19:07:13 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D28948 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot o= rg --- Comment #1 from Tom Tromey --- 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. --=20 You are receiving this mail because: You are on the CC list for the bug.=