[Bug gdb/29587] New: [gdb/cli] Add maintenance command to poison certain commands

[Bug gdb/29587] New: [gdb/cli] Add maintenance command to poison certain commands

[vries at gcc dot gnu.org]

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.

[Bug gdb/29587] [gdb/cli] Add maintenance command to poison certain commands

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=29587

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
This seems tricky for the case of "break *", because the
command is really just "break".  Maybe for this one an
ad-hoc flag would be simpler.

-- 
You are receiving this mail because:
You are on the CC list for the bug.