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 C15873858406; Mon, 10 Oct 2022 08:58:14 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C15873858406
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1665392294;
	bh=k0HhiYUNOM/Aq0dbhlPcAH9m3TVavuF2NOuifh5HQ3A=;
	h=From:To:Subject:Date:From;
	b=K0zQ9XPLz3itamjSdZKrhPNQKH9+vMwdL3Mme2X/8CKp4/P/atQWfw8TSvvDrs/sd
	 8xnY8T452hO395FW5p2s/Z0MwYFSkh4G9L7WO+x41iSpiwrMaar0ysswaAMvBMs7+Z
	 P8HC+NaTDIks0ruMohmS1zj8G2XNxPnMtrrN8QH8=
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/29664] New: [gdb/testsuite, taskset -c 0] FAIL:
 gdb.base/style.exp: capture_command_output for x/1i *main
Date: Mon, 10 Oct 2022 08:58:14 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.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: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-29664-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=3D29664

            Bug ID: 29664
           Summary: [gdb/testsuite, taskset -c 0] FAIL:
                    gdb.base/style.exp: capture_command_output for x/1i
                    *main
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

When running test-case gdb.base/style.exp with taskset -c 0, I run into:
...
(gdb) PASS: gdb.base/style.exp: have style markers when Pygments is working
fine
python^M
>def replacement_colorize_disasm(content,gdbarch):^M
>  return None^M
>gdb.styling.colorize_disasm =3D replacement_colorize_disasm^M
>quit^M
(gdb) PASS: gdb.base/style.exp: setup replacement colorize_disasm function
^M
(gdb) FAIL: gdb.base/style.exp: capture_command_output for x/1i *main
x/1i *main^M
   ^[[34m0x4004b2^[[m <^[[33mmain^[[m>: push   %rbp^M
(gdb) PASS: gdb.base/style.exp: have no style markers when Pygments is brok=
en
...

Without taskset -c 0, we have instead:
...
(gdb) PASS: gdb.base/style.exp: have style markers when Pygments is working
fine
python^M
>def replacement_colorize_disasm(content,gdbarch):^M
>  return None^M
>gdb.styling.colorize_disasm =3D replacement_colorize_disasm^M
>quit^M
(gdb) ^M
(gdb) PASS: gdb.base/style.exp: setup replacement colorize_disasm function
x/1i *main^M
   ^[[34m0x4004b2^[[m <^[[33mmain^[[m>: push   %rbp^M
(gdb) PASS: gdb.base/style.exp: have no style markers when Pygments is brok=
en
...

Note that the "PASS: gdb.base/style.exp: setup replacement colorize_disasm
function" in the latter case consumes two prompts, but in the former case o=
nly
one.

At this point, I don't understand why we see two prompts in the first place.

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