From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 944AF388CC04; Tue, 1 Dec 2020 13:08:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 944AF388CC04 From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug testsuite/26990] New: [-m32] FAIL: gdb.arch/amd64-gs_base.exp: print fs_base Date: Tue, 01 Dec 2020 13:08:26 +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: 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: Tue, 01 Dec 2020 13:08:26 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D26990 Bug ID: 26990 Summary: [-m32] FAIL: gdb.arch/amd64-gs_base.exp: print fs_base 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: --- With target board unix/-m32, I see: ... FAIL: gdb.arch/amd64-gs_base.exp: print fs_base FAIL: gdb.arch/amd64-gs_base.exp: print gs_base FAIL: gdb.arch/amd64-gs_base.exp: info registers fs_base and gs_base with v= alue ... In more detail: ... (gdb) print /x $fs_base^M $1 =3D void^M (gdb) FAIL: gdb.arch/amd64-gs_base.exp: print fs_base print /x $gs_base^M $2 =3D void^M (gdb) FAIL: gdb.arch/amd64-gs_base.exp: print gs_base print $fs_base =3D 2^M $3 =3D 2^M (gdb) PASS: gdb.arch/amd64-gs_base.exp: set fs_base print $gs_base =3D 3^M $4 =3D 3^M (gdb) PASS: gdb.arch/amd64-gs_base.exp: set gs_base info register sys^M orig_eax 0xffffffff -1^M (gdb) FAIL: gdb.arch/amd64-gs_base.exp: info registers fs_base and gs_base = with value ... Using maint print xml-tdesc, we can see the presence of fs_base for -m64: ... $ gcc hello.c $ gdb -batch a.out -ex start -ex "maint print xml-tdesc" \ | grep -i fs_base $ ... and -m32: ... $ gcc hello.c -m32 $ gdb -batch a.out -ex start -ex "maint print xml-tdesc" \ | grep -i fs_base $ ... So, we should just make this unsupported for -m32, instead of failing. --=20 You are receiving this mail because: You are on the CC list for the bug.=