Hide Forgot
Description of problem: This error happens every time I run makensis. These are the last few lines of output before it segfaults. FileOpen: $INSTDIR\app.running.lck as a -> $R0 !insertmacro: _If !insertmacro: end of _If MessageBox: 48: "CompassGo is running. Please close it first" Abort: "" !insertmacro: _Else !insertmacro: end of _Else FileClose: $R0 Delete: "$INSTDIR\app.running.lck" !insertmacro: _EndIf !insertmacro: end of _EndIf FunctionEnd Processed 1 file, 1 command line command, writing output: Processing pages... Done! Removing unused resources... Done! Generating language tables... Done! Segmentation fault (core dumped) Version-Release number of selected component: mingw32-nsis-2.46-9.fc19 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/makensis '-XOutFile /home/ben/dev/projects/compass/compass/mobile/target/mobile-0.2.3-Caresource-SNAPSHOT-patch-min.exe' -V2 /home/ben/dev/projects/compass/compass/mobile/target/resources/installer/nullsoft_installer_patch_min.nsi crash_function: CResourceEditor::WriteRsrcSec executable: /usr/bin/makensis kernel: 3.11.4-201.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #0 CResourceEditor::WriteRsrcSec at Source/ResourceEditor.cpp:757 #1 CResourceEditor::Save at Source/ResourceEditor.cpp:514 #2 CEXEBuild::close_res_editor at Source/build.cpp:3379 #3 CEXEBuild::write_output at Source/build.cpp:2449 Potential duplicate: bug 948074
Created attachment 819129 [details] File: backtrace
Created attachment 819130 [details] File: cgroup
Created attachment 819131 [details] File: core_backtrace
Created attachment 819132 [details] File: dso_list
Created attachment 819133 [details] File: environ
Created attachment 819134 [details] File: exploitable
Created attachment 819135 [details] File: limits
Created attachment 819136 [details] File: maps
Created attachment 819137 [details] File: open_fds
Created attachment 819138 [details] File: proc_pid_status
Created attachment 819139 [details] File: var_log_messages
*** This bug has been marked as a duplicate of bug 948074 ***