Bug 2209105 - [abrt] less: create_hilites(): less killed by SIGSEGV
Summary: [abrt] less: create_hilites(): less killed by SIGSEGV
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: less
Version: 38
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matej Mužila
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:5843cd4512d81d911176536fe4c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-22 16:20 UTC by Jonathan Ryshpan
Modified: 2023-08-02 19:42 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)
File: cpuinfo (2.68 KB, text/plain)
2023-05-22 16:20 UTC, Jonathan Ryshpan
no flags Details
File: open_fds (209 bytes, text/plain)
2023-05-22 16:20 UTC, Jonathan Ryshpan
no flags Details
File: core_backtrace (3.54 KB, text/plain)
2023-05-22 16:20 UTC, Jonathan Ryshpan
no flags Details
File: os_info (699 bytes, text/plain)
2023-05-22 16:20 UTC, Jonathan Ryshpan
no flags Details
File: exploitable (81 bytes, text/plain)
2023-05-22 16:20 UTC, Jonathan Ryshpan
no flags Details
File: maps (2.68 KB, text/plain)
2023-05-22 16:20 UTC, Jonathan Ryshpan
no flags Details
File: proc_pid_status (1.38 KB, text/plain)
2023-05-22 16:20 UTC, Jonathan Ryshpan
no flags Details
File: environ (4.35 KB, text/plain)
2023-05-22 16:20 UTC, Jonathan Ryshpan
no flags Details
File: dso_list (506 bytes, text/plain)
2023-05-22 16:20 UTC, Jonathan Ryshpan
no flags Details
File: mountinfo (3.93 KB, text/plain)
2023-05-22 16:20 UTC, Jonathan Ryshpan
no flags Details
File: limits (1.29 KB, text/plain)
2023-05-22 16:20 UTC, Jonathan Ryshpan
no flags Details
File: backtrace (19.67 KB, text/plain)
2023-05-22 16:21 UTC, Jonathan Ryshpan
no flags Details
Core dump of the crash of less (476.00 KB, application/x-core)
2023-07-03 19:23 UTC, Jonathan Ryshpan
no flags Details
Coredumpctl output on console while producing less-coredump (2.30 KB, text/plain)
2023-07-03 19:26 UTC, Jonathan Ryshpan
no flags Details

Description Jonathan Ryshpan 2023-05-22 16:20:40 UTC
Description of problem:
I ran
$ locate -i bluetooth | less
In less, I searched for "!home"; less crashed.

Version-Release number of selected component:
less-633-1.fc38

Additional info:
reporter:       libreport-2.17.10
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.kde.konsole-428b45ed4a9a4311ad14fb8889463ab1.scope
backtrace_rating: 4
cmdline:        less
crash_function: create_hilites
runlevel:       N 5
type:           CCpp
kernel:         6.2.15-300.fc38.x86_64
uid:            1000
reason:         less killed by SIGSEGV
package:        less-633-1.fc38
executable:     /usr/bin/less
journald_cursor: s=9e8facd94e854bbf924ea4e24e7df513;i=2ec75;b=62c8ee2bf7674bbda295652111046414;m=221a7187df;t=5fc4a8e32df4a;x=68e08c8630d4dbdb
rootdir:        /

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 create_hilites at /usr/src/debug/less-633-1.fc38.x86_64/search.c:895
 #1 hilite_line.constprop.0 at /usr/src/debug/less-633-1.fc38.x86_64/search.c:960
 #2 search_range at /usr/src/debug/less-633-1.fc38.x86_64/search.c:1357
 #3 prep_hilite at /usr/src/debug/less-633-1.fc38.x86_64/search.c:1758
 #4 forw_line_seg at /usr/src/debug/less-633-1.fc38.x86_64/input.c:112
 #5 repaint_hilite at /usr/src/debug/less-633-1.fc38.x86_64/search.c:274
 #6 search at /usr/src/debug/less-633-1.fc38.x86_64/search.c:1556
 #7 multi_search.constprop.0 at /usr/src/debug/less-633-1.fc38.x86_64/command.c:1104
 #8 mca_char at /usr/src/debug/less-633-1.fc38.x86_64/command.c:704
 #9 commands at /usr/src/debug/less-633-1.fc38.x86_64/command.c:1275

Comment 1 Jonathan Ryshpan 2023-05-22 16:20:43 UTC
Created attachment 1966248 [details]
File: cpuinfo

Comment 2 Jonathan Ryshpan 2023-05-22 16:20:45 UTC
Created attachment 1966249 [details]
File: open_fds

Comment 3 Jonathan Ryshpan 2023-05-22 16:20:46 UTC
Created attachment 1966250 [details]
File: core_backtrace

Comment 4 Jonathan Ryshpan 2023-05-22 16:20:48 UTC
Created attachment 1966251 [details]
File: os_info

Comment 5 Jonathan Ryshpan 2023-05-22 16:20:50 UTC
Created attachment 1966252 [details]
File: exploitable

Comment 6 Jonathan Ryshpan 2023-05-22 16:20:51 UTC
Created attachment 1966253 [details]
File: maps

Comment 7 Jonathan Ryshpan 2023-05-22 16:20:53 UTC
Created attachment 1966254 [details]
File: proc_pid_status

Comment 8 Jonathan Ryshpan 2023-05-22 16:20:54 UTC
Created attachment 1966255 [details]
File: environ

Comment 9 Jonathan Ryshpan 2023-05-22 16:20:56 UTC
Created attachment 1966256 [details]
File: dso_list

Comment 10 Jonathan Ryshpan 2023-05-22 16:20:57 UTC
Created attachment 1966257 [details]
File: mountinfo

Comment 11 Jonathan Ryshpan 2023-05-22 16:20:59 UTC
Created attachment 1966258 [details]
File: limits

Comment 12 Jonathan Ryshpan 2023-05-22 16:21:00 UTC
Created attachment 1966259 [details]
File: backtrace

Comment 13 Matej Mužila 2023-05-30 13:00:06 UTC
Hi, thank you for report.

Unfortunately I'm not able to reproduce the problem. Does the problem occur everytime? If so, could you please provide output of "locate -i bluetooth" (locate -i bluetooth > filename.txt)?

Comment 14 Jonathan Ryshpan 2023-05-30 20:01:05 UTC
I cannot repeat the problem today, though it happened several times, both with 
    $ locate -i bluetooth | less
and with other similar invocations of the form
    $ locate -i <XXX> | less
on the day I reported it.

Foo!

Comment 15 Matej Mužila 2023-05-31 11:49:30 UTC
Unfortunately, if I can't reproduce it, I can't fix it.

I you were able to provide a coredump from that particular crash, I might be able to identify the bug and fix it eventually.

You can list `less` coredumps stored on your system:
  $ coredumpctl list /usr/bin/less

It will output list of coredumps captured in the journal.
If you can find an entry with matching timestamp and *with* COREFILE column saying "present", then run:
  $ coredumpctl dump --output <NEW-FILENAME> /usr/bin/less <PID>

  Where <NEW-FILENAME> is filename (or path) of the coredump file to be created, <PID> is the PID from the matching entry from previous command.

Please be aware, that the coredump file may contain the data that was opened by/piped to less when it was executed (in this particular case the
output of "locate -i <XXX>") [1].

If you can create the coredump and you are ok with its content being public, please attach it to this bug.

---

[1] https://en.wikipedia.org/wiki/Core_dump

Comment 16 Jonathan Ryshpan 2023-07-03 19:23:05 UTC
Created attachment 1973909 [details]
Core dump of the crash of less

Comment 17 Jonathan Ryshpan 2023-07-03 19:26:39 UTC
Created attachment 1973920 [details]
Coredumpctl output on console while producing less-coredump

Comment 18 Carl 2023-08-02 19:42:58 UTC
open any file in less, press / and then ! to do a non-match search, non-search for any char or string that will match a line in the file. boom


reporter:       libreport-2.17.11
type:           CCpp
reason:         less killed by SIGSEGV
journald_cursor: s=882be8df477c4c6496abc167b89cee28;i=41751;b=5f5589de0eb747e5b1c5abac3ef78a37;m=f74ca02ea;t=601f506380142;x=3e016da545a0ff7c
executable:     /usr/bin/less
cmdline:        less /tmp/model-results-violations-1691001633012.txt
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.gnome.Terminal.slice/gnome-terminal-server.service
rootdir:        /
uid:            1000
kernel:         6.4.4-200.fc38.x86_64
package:        less-633-1.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: create_hilites
comment:        open any file in less, press / and then ! to do a non-match search, non-search for any char or string that will match a line in the file. boom


Note You need to log in before you can comment on or make changes to this bug.