From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C7D8F3858CDB; Mon, 6 Feb 2023 12:30:34 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C7D8F3858CDB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1675686634; bh=4VpVX9KSzp3MeVVzcgJHOHL8iFcPUv8MCiijnKNib9E=; h=From:To:Subject:Date:In-Reply-To:References:From; b=H86TDv9fAaRcIcamq11N1Yk3621/6BIRu/6+GgokKs83VSGNx/V1k4Jh3VhNZ4aC+ 8ilr22+Hc0o9vXmX0niS+DezBgEnAWPQNtQfDTGjiGtYQwpwMVR0TeRvOfZOutrIw/ HGnDPy27RI6Sp+GgfVbav7RIdMydprybxov6EPxQ= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug record/30073] [intel Efficient-core] FAIL: gdb.btrace/exception.exp: flat (pattern 1) Date: Mon, 06 Feb 2023 12:30:34 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: unknown 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: Message-ID: In-Reply-To: References: 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: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30073 --- Comment #2 from Tom de Vries --- This is without libipt: ... configure:25703: checking for libipt configure:25722: gcc -o conftest -O0 -g -O0 -g -Wall conftest.c -lncursesw -lm -ldl -lipt >&5 conftest.c:178:10: fatal error: intel-pt.h: No such file or directory ... configure:25732: result: no configure:25759: WARNING: libipt is missing or unusable; some features may = be unavailable. ... With libipt (using latest release v2.0.5) the two test-cases pass. --=20 You are receiving this mail because: You are on the CC list for the bug.=