Description of problem: submitted malformed dialog commandline. Resolved before ABRT presented notification so I dont have the submitted arg file. Version-Release number of selected component: dialog-1.2-4.20130902.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: dialog --title 'Only 1 candidate device found' --file /tmp/rpi2 --yesno 15 50 --defaultno crash_function: unescape_argv executable: /usr/bin/dialog kernel: 3.12.10-300.fc20.x86_64 runlevel: unknown type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (1 frames) #0 unescape_argv at dialog.c:369
Created attachment 864303 [details] File: backtrace
Created attachment 864304 [details] File: cgroup
Created attachment 864305 [details] File: core_backtrace
Created attachment 864306 [details] File: dso_list
Created attachment 864307 [details] File: environ
Created attachment 864308 [details] File: exploitable
Created attachment 864309 [details] File: limits
Created attachment 864310 [details] File: maps
Created attachment 864311 [details] File: open_fds
Created attachment 864312 [details] File: proc_pid_status
Created attachment 864313 [details] File: var_log_messages
I can reproduce it with dialog --file <(echo aaa) --yesno 15 50 The latest upstream dialog (20140112) seems to crash too. CCing upstream maintainer.
I see - basically the problem is that the cases I tested all had more than one token (so the adjustment-loop is wrong). will fix...
I've uploaded a fixed version.
Thanks, Thomas.
no problem (report bugs)