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 5954D3853D4E; Mon, 28 Nov 2022 20:41:48 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5954D3853D4E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1669668108;
	bh=34vMRdVdI9PfjDHvrDklGIgrgvR7uSimk2WFZ9vqE1k=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=B6XCPPPVKghMF+z/5W4bzA43ZzgDMyePlw9RZzy2Bp/DvcoSbSQP3iuekdMs+ouB8
	 li5ncmBG+uquu5PNJB248mF0/ocRAuOw7N4VPYS6ljIxqfp5JeOteGAqtC0TKAaPhX
	 ONgQwssSOq5BGe+9z3GmL7YmbwI5UXRTKl5Q6onE=
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29787] Using "set debug infrun on" and "set logging
 enabled" breaks GDB prompt and makes GDB crash
Date: Mon, 28 Nov 2022 20:41:47 +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: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: tromey at sourceware dot org
X-Bugzilla-Target-Milestone: 13.1
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-29787-4717-N1gTFCPJwx@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-29787-4717@http.sourceware.org/bugzilla/>
References: <bug-29787-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
List-Id: <gdb-prs.sourceware.org>

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

--- Comment #9 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gn=
u.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D1dd889362bb7=
027ebea754a161bf629270cc9042

commit 1dd889362bb7027ebea754a161bf629270cc9042
Author: Tom Tromey <tromey@adacore.com>
Date:   Thu Nov 17 10:24:38 2022 -0700

    Don't let gdb_stdlog use pager

    When using the "set logging" commands, cli_interp_base::set_logging
    will send gdb_stdlog output (among others) to the tee it makes for
    gdb_stdout.  However, this has the side effect of also causing logging
    to use the pager.  This is PR gdb/29787.

    This patch fixes the problem by keeping stderr and stdlog separate
    from stdout, preserving the rule that only gdb_stdout should page.

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

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