From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 7BD8E3858C52; Fri, 12 Aug 2022 17:23:23 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7BD8E3858C52
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: Fri, 12 Aug 2022 17:23:23 +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: 
Message-ID: <bug-28948-4717-P4VQUNig6x@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-28948-4717@http.sourceware.org/bugzilla/>
References: <bug-28948-4717@http.sourceware.org/bugzilla/>
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 <gdb-prs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-prs/>
List-Help: <mailto:gdb-prs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2022 17:23:23 -0000

https://sourceware.org/bugzilla/show_bug.cgi?id=3D28948

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
After deeper investigation I found some problems with my idea.
The basic issue is that there's no good spot to put the logging:

If the logging is early, then anything logged won't be wrapped
in MI output formatting.
However, if the logging is late, then it won't happen at all
for the TUI, since it normally doesn't really use the output
stream at all.

Maybe it can be salvaged somehow.


For the TUI, I tend to think we should merge the TUI and CLI interps.
That might eliminate some of the weirdness.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=