[Bug testsuite/29664] New: [gdb/testsuite, taskset -c 0] FAIL: gdb.base/style.exp: capture_command_output for x/1i *main

["vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

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

            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 = 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 broken
...

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 = 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 broken
...

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 only
one.

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

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