public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.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 [thread overview] Message-ID: <bug-30103-4717-QbEsz9pbzE@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30103-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30103 Tom de Vries <vries at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|gdb |testsuite --- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> --- 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 that 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. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-10 11:07 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-09 16:31 [Bug gdb/30103] New: " luis.machado at arm dot com 2023-02-09 16:32 ` [Bug gdb/30103] " luis.machado at arm dot com 2023-02-10 11:07 ` vries at gcc dot gnu.org [this message] 2023-02-10 14:58 ` [Bug testsuite/30103] " cvs-commit at gcc dot gnu.org 2023-02-10 14:59 ` vries at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-30103-4717-QbEsz9pbzE@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).