[Bug ada/25769] New: gdb not to drop to Multiple matches prompt with -batch

["vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

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

            Bug ID: 25769
           Summary: gdb not to drop to Multiple matches prompt with -batch
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: ada
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

Consider test-case gdb.ada/call_pn.exp, run with target board
unix/-flto/-O0/-flto-partition=none/-ffat-lto-objects.

When using the executable like this, we get:
...
$ gdb -batch ./outputs/gdb.ada/call_pn/foo -ex "print last_node_id"
Multiple matches for last_node_id
[0] cancel
[1] pck.last_node_id at
/data/gdb_versions/devel/binutils-gdb.git/gdb/testsuite/gdb.ada/call_pn/pck.adb:17
[2] pck.last_node_id at
/data/gdb_versions/devel/binutils-gdb.git/gdb/testsuite/gdb.ada/call_pn/pck.adb:17
> 
...

After typing 0, enter, enter:
...
> 0

cancelled
$
...
and we're done.

The -batch option is supposed to act as if "set confirm off" were in effect,
and that is documented as:
...
set confirm off

    Disables confirmation requests.
...

So I suppose that this behaviour is not wrong, since we're asking a choice
rather than a confirmation, but it's counter-intuitive for me.

I intuitively interpret -batch as "not requiring user input" so automatically
choosing 0 or printing all options would have made more sense for me.

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