From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C53253858414; Fri, 10 Feb 2023 11:07:07 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C53253858414 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1676027227; bh=3VDpixwH53YywrntLTuctM/kbhFsUuhpaRmnp+DBT4E=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Fp8NNvfpCFO7dVjm8Tg3soIv2RbAdLm4IbJ/QhUv5nfAPuos0GdOqrWMdzc7LwxQm ZCMnP+xSoCFEcSuCqBUyP91JXfza5t5CRUHCDx/UBJuUjPVxgDEN0hdnmEiJGwJc74 oT0MXQFMZckOrro7IdZemltQexFWpa5xDyRajbQ8= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug testsuite/30103] GDB gets confused about what is the current source file for various actions Date: Fri, 10 Feb 2023 11:07:07 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed 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: component 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=3D30103 Tom de Vries changed: What |Removed |Added ---------------------------------------------------------------------------- Component|gdb |testsuite --- Comment #2 from Tom de Vries --- I don't think this is a gdb problem, but a testsuite problem. I think the fact that the test-case source file is called longjmp.c, and th= at due to a KFAIL we're stopping in __libc_siglongjmp, which is in a glibc file also called longjmp.c is an unfortunate red herring. In other words, I think we would see the same problem if __libc_siglongjmp = was located in bla.c (or, conversely we'd rename the test-case source file). Setting component to testsuite. Subbmitted patch: https://sourceware.org/pipermail/gdb-patches/2023-February/196807.html. Btw, as mentioned in the patch, I also managed to reproduce on x86_64/-m32. --=20 You are receiving this mail because: You are on the CC list for the bug.=