srfsh can segfault if .srfsh_history is empty
Bug #1461978 reported by
Galen Charlton
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenSRF |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
If ~/.srfsh_history is empty (as might happen if one cleared the request history by cat'ing /dev/null into it), using readline commands to try to retrieve history items causes srfsh to segfault.
For example:
$ cat /dev/null > ~/.srfsh_history
$ srfsh # then hit the up arrow key
OpenSRF master
tags: | added: pullrequest |
Changed in opensrf: | |
status: | New → Confirmed |
To post a comment you must log in.
Note that a segfault does not happen if ~/.srfsh_history was not present to begin with.