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 gdb/29587] New: [gdb/cli] Add maintenance command to poison certain commands Date: Tue, 20 Sep 2022 08:30:16 +0000 [thread overview] Message-ID: <bug-29587-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29587 Bug ID: 29587 Summary: [gdb/cli] Add maintenance command to poison certain commands Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- There was a discussion related to commit 52b920c5d20 ("[gdb/testsuite] Fix gdb.dwarf2/dw2-dir-file-name.exp for ppc64le") that the test-case shouldn't use break *function, and actually the entire testsuite, because on powerpc that can lead to trouble with the local/global entrypoint, and breakpoints not triggering when you expect them to. If we'd have a command, say: ... (gdb) maint poision "break *" ... then we could add this to the normal gdb testsuite starting commands, to prevent this construct slipping in accidentally. Then only test-cases that actually intend to test that construct should de-poison the command at the start of the test-case. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-09-20 8:30 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-20 8:30 vries at gcc dot gnu.org [this message] 2022-12-06 16:42 ` [Bug gdb/29587] " tromey at sourceware dot 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-29587-4717@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).