Description of problem: Just using msiinfo to check a file causes a segmentaton fault Version-Release number of selected component: msitools-0.92.26-1.fc19 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: msiinfo suminfo 'TOSHIBA Value Added Package.msi' crash_function: __strcmp_sse4_2 executable: /usr/bin/msiinfo kernel: 3.11.6-200.fc19.i686 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 __strcmp_sse4_2 at ../sysdeps/i386/i686/multiarch/strcmp-sse4.S:262 #1 find_insert_index at string.c:176 #2 insert_string_sorted at string.c:192 #3 set_st_entry at string.c:216 #4 msi_addstring at string.c:294 #5 msi_load_string_table at string.c:540 #6 _libmsi_database_open at libmsi-database.c:2201 #7 init at libmsi-database.c:2575 #8 libmsi_database_new at libmsi-database.c:2618 #9 cmd_suminfo at tools/msiinfo.c:302
Created attachment 820315 [details] File: backtrace
Created attachment 820316 [details] File: cgroup
Created attachment 820317 [details] File: core_backtrace
Created attachment 820318 [details] File: dso_list
Created attachment 820319 [details] File: exploitable
Created attachment 820320 [details] File: limits
Created attachment 820321 [details] File: maps
Created attachment 820322 [details] File: open_fds
Created attachment 820323 [details] File: proc_pid_status
Created attachment 820324 [details] File: var_log_messages
thanks, could you provide a link to the MSI file?
Yes, I'll upload the MSI file rigth away.
Created attachment 821512 [details] the MSI that triggered the bug
I have pushed a fix, but I wonder if there isn't more to fix to handle the ForceCodePage property correctly. Nevertheless, this is enough to fix the crash: https://git.gnome.org/browse/msitools/commit/?id=e02b155b332df452a9df86984e11eb8a1772aa86
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.