Hello Mark, Tks for reviewing my mistake. I believe it is good now.
inaddy@lp1530837trusty:~/Codes/bugs/1530837/trusty/corosync-2.3.3$ patch -p1 < ../trusty_corosync_2.3.3-1ubuntu2.debdiff patching file debian/changelog patching file debian/patches/Fix-compiler-warning-introduced-by-previous-patch.patch patching file debian/patches/fix-memory-leak-produced-by-corosync-v.patch patching file debian/patches/Handle-SIGSEGV-and-SIGABRT-signals.patch patching file debian/patches/series inaddy@lp1530837trusty:~/Codes/bugs/1530837/trusty/corosync-2.3.3$ quilt push -a Applying patch fix-memory-leak-produced-by-corosync-v.patch patching file exec/main.c Applying patch Handle-SIGSEGV-and-SIGABRT-signals.patch patching file exec/main.c Applying patch Fix-compiler-warning-introduced-by-previous-patch.patch patching file exec/main.c Now at patch Fix-compiler-warning-introduced-by-previous-patch.patch Thank you! Rafael -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530837 Title: Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running corosync -v To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1530837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
