Step 1: Launch gdb Step 2: Type "enable count" Observed behaviour: gdb crashes Expected behaviour: gdb tells me subtly that I should go back to school and learn to read better.
[PATCH] "enable count" user input error handling (PR gdb/15678) http://sourceware.org/ml/gdb-patches/2013-06/msg00788.html
Patch here: http://sourceware.org/ml/gdb-patches/2013-06/msg00788.html Waiting for copyright assignment to come through.
The master branch has been updated by Simon Marchi <simark@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b9d6130764916fac3d9bcfde2d672053a0ef3316 commit b9d6130764916fac3d9bcfde2d672053a0ef3316 Author: Simon Marchi <simon.marchi@ericsson.com> Date: Mon Feb 2 14:57:31 2015 -0500 "enable count" user input error handling (PR gdb/15678) Typing "enable count" by itself crashes GDB. Also, if you omit the breakpoint number/range, the error message is not very clear: (gdb) enable count 2 warning: bad breakpoint number at or near '' (gdb) enable count Segmentation fault (core dumped) With this patch, the error messages are slightly more helpful: (gdb) enable count 2 Argument required (one or more breakpoint numbers). (gdb) enable count Argument required (hit count). gdb/ChangeLog: PR gdb/15678 * breakpoint.c (map_breakpoint_numbers): Check for empty args string. (enable_count_command): Check args for NULL value. gdb/testsuite/ChangeLog: PR gdb/15678 * gdb.base/ena-dis-br.exp: Test "enable count" for bad user input.
Fixed by patch above.