aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLibravatar Unit 193 <unit193@ubuntu.com>2016-03-18 16:58:57 -0400
committerLibravatar Unit 193 <unit193@ubuntu.com>2016-03-18 16:58:57 -0400
commitccda46ad88850f741f8e7e6e46d752b28de8e375 (patch)
tree3bea1057c00cde2a31b96e2e70717f4eeb621986
parent9813fd25016a351d91a6db535c5622450099e579 (diff)
downloadveracrypt-ccda46ad88850f741f8e7e6e46d752b28de8e375.tar.bz2
veracrypt-ccda46ad88850f741f8e7e6e46d752b28de8e375.tar.xz
veracrypt-ccda46ad88850f741f8e7e6e46d752b28de8e375.tar.zst
d/p/004-gcc5-compatibility.diff: Add a patch from upstream fixing GCC5 compatibility.
-rw-r--r--debian/patches/004-gcc5-compatibility.diff54
-rw-r--r--debian/patches/series1
2 files changed, 55 insertions, 0 deletions
diff --git a/debian/patches/004-gcc5-compatibility.diff b/debian/patches/004-gcc5-compatibility.diff
new file mode 100644
index 0000000..b64bbb6
--- /dev/null
+++ b/debian/patches/004-gcc5-compatibility.diff
@@ -0,0 +1,54 @@
+From 646679da4d79bf7f8af22c44c7ae8498086a88a6 Mon Sep 17 00:00:00 2001
+From: Mounir IDRASSI <mounir.idrassi@idrix.fr>
+Date: Fri, 18 Mar 2016 16:25:48 +0100
+Subject: [PATCH] Linux: Completely fix gcc-5 "Invalid characters encountered"
+ issue on mount. It was caused by an issue of gcc-5 STL implementation that is
+ causing char* pointers retrieved from std::string using c_str method to
+ become invalid in the child of a child process (after two fork calls). The
+ workaround is to first copy the std:string values in the child before calling
+ the second fork.
+
+---
+ src/Platform/Unix/Process.cpp | 24 ++++++++++++++++++++++--
+ 1 file changed, 22 insertions(+), 2 deletions(-)
+
+diff --git a/src/Platform/Unix/Process.cpp b/src/Platform/Unix/Process.cpp
+index 388bda6..0770364 100644
+--- a/src/Platform/Unix/Process.cpp
++++ b/src/Platform/Unix/Process.cpp
+@@ -53,13 +53,33 @@ namespace VeraCrypt
+ try
+ {
+ int argIndex = 0;
++ /* Workaround for gcc 5.X issue related to the use of STL (string and list) with muliple fork calls.
++ *
++ * The char* pointers retrieved from the elements of parameter "arguments" are no longer valid after
++ * a second fork is called. "arguments" was created in the parent of the current child process.
++ *
++ * The only solution is to copy the elements of "arguments" parameter in a local string array on this
++ * child process and then use char* pointers retrieved from this local copies before calling fork.
++ *
++ * gcc 4.x doesn't suffer from this issue.
++ *
++ */
++ string argsCopy[array_capacity (args)];
+ if (!execFunctor)
+- args[argIndex++] = const_cast <char*> (processName.c_str());
++ {
++ argsCopy[argIndex++] = processName;
++ }
+
+ foreach (const string &arg, arguments)
+ {
+- args[argIndex++] = const_cast <char*> (arg.c_str());
++ argsCopy[argIndex++] = arg;
+ }
++
++ for (int i = 0; i < argIndex; i++)
++ {
++ args[i] = const_cast <char*> (argsCopy[i].c_str());
++ }
++
+ args[argIndex] = nullptr;
+
+ if (inputData)
diff --git a/debian/patches/series b/debian/patches/series
index 2694b0b..c7b7c51 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
001-user-guide-location.diff
002-build-flags.diff
003-indicator-support.diff
+004-gcc5-compatibility.diff