Red Hat Bugzilla – Bug 979688
[abrt] dialog-1.1-17.20120706.fc18: strlen: Process /usr/bin/dialog was killed by signal 11 (SIGSEGV)
Last modified: 2013-07-11 23:05:11 EDT
Version-Release number of selected component:
cmdline: dialog --help-button --ok-label Edit --cancel-label Exit --extra-button --extra-label Save --menu 'Current Gammu configuration' 0 0 0 P 'Port (00:23:F1:FD:45:2E)' C 'Connection (blueat)' M 'Model ()' D 'Synchronize time (yes)' F 'Log file ()' O 'Log format (nothing)' L 'Use locking ()' G 'Gammu localisation ()'
runlevel: N 5
Thread no. 1 (8 frames)
#0 strlen at ../sysdeps/i386/i686/multiarch/strlen-sse2-bsf.S:50
#1 dlg_count_wchars at inputstr.c:300
#3 dlg_index_wchars at inputstr.c:336
#4 print_tag at menubox.c:90
#5 print_item at menubox.c:155
#6 dlg_menu at menubox.c:447
#7 dialog_menu at menubox.c:804
#8 call_menu at dialog.c:656
Created attachment 766865 [details]
Created attachment 766866 [details]
Created attachment 766867 [details]
Created attachment 766868 [details]
Created attachment 766869 [details]
Created attachment 766870 [details]
Created attachment 766871 [details]
Created attachment 766872 [details]
Created attachment 766874 [details]
Created attachment 766877 [details]
I recall making a fix in this area based on coverity and clang -
probably the latter - referring to a problem with strlen of a null
value. The current version is 1.2-20130523
I wasn't able to reproduce it by running the command from the comment #0, but in the backtrace there is a strlen call on NULL. I can make an f18 update to the latest dialog if it fixes the problem.
An f19 build here
The diagnostic (my check-in comment only noted the tool which found the issue) seemed to point to a case which wasn't likely. If it had been easy to reproduce,
or otherwise changed visible behavior, I would have added
more info about it, as I did for three items here:
(citing each small change would make the log 3-4 times as long, and
make it harder to see important stuff).
dialog-1.2-2.20130523.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dialog-1.2-2.20130523.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
dialog-1.2-2.20130523.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.