[Bug cli/28665] CLI commands that cause crash

["aburgess at redhat dot com" <sourceware-bugzilla@sourceware.org>]

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

Andrew Burgess <aburgess at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2021-12-07
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1
                 CC|                            |aburgess at redhat dot com

--- Comment #1 from Andrew Burgess <aburgess at redhat dot com> ---
The `list task 123` problem is a result of "task" being a linespec keyword. 
GDB parses the linespec 'task 123' and stops when it sees the keyword 'task'.

As a result the event_location::u::linespec_location::spec_string is left as
nullptr.

Later in event_location_to_sals, the spec_string is passed to parse_linespec,
which doesn't check for the incoming string being nullptr.

The error will reproduce for any location that starts with a keyword, e.g. 

  (gdb) list if (1)
  **crash**

  (gdb) list thread 1
  **crash**

  (gdb) list -force-condition
  **crash**

This seems to be a long standing issue with the location/linespec parsing, its
present at least as far back as the gdb 8.x series.

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