truecrypt and truecrypt-3.0 binaries cause linker error: cannot locate symbol __exidx_end

[neurodroid]

From anilkpa...@gmail.com on November 25, 2012 00:42:01

What steps will reproduce the problem? 1. Launch terminal with Expert->Start root terminal

1. Enter "truecrypt" at terminal command prompt.
   NOTE: Also get the same results with downloaded truecrypt-3.0 What is the expected output? What do you see instead? Expected truecrypt binary to load and provide usage options.
   Result: I see the following error message:
   soinfo_relocate(linker.cpp:975): cannot locate symbol "__exidx_end" referenced by "truecrypt"...CANNOT LINK EXECUTABLE What version of the product are you using? On what operating system? 0.7.6 on Android 4.2 Please provide any additional information below. Device is Google Nexus 4 running Android version 4.2 with unlocked bootloader and root installed.

Original issue: http://code.google.com/p/cryptonite/issues/detail?id=46

[neurodroid]

From n...@google.com on November 27, 2012 13:18:14

truecrypt team: Please try recompiling your app with Android NDK r8b or greater. This will fix this bug.

[neurodroid]

From christoph.schmidthieber@gmail.com on November 27, 2012 13:22:12

Thanks for the report, and thanks for suggesting a fix. Will rebuild with r8c.

Status: Accepted
Owner: christoph.schmidthieber@gmail.com
Labels: -Priority-Medium Priority-High

[neurodroid]

From christoph.schmidthieber@gmail.com on November 27, 2012 13:38:37

@anilkpatel: Could you test the encfs binary that ships with 0.7.6? It's been built with r8c and shouldn't produce this error.
TrueCrypt had to be built with Crystax NDK 7 because of incomplete wchar support in the official NDK. It's a known problem: http://www.crystax.net/trac/ndk/ticket/112 If it can't be resolved on the Crystax side, we'll have to switch to the official NDK and find a wchar workaround.

[neurodroid]

From anilkpa...@gmail.com on November 27, 2012 13:43:11

On testing the encfs binary on 0.7.6, here is what I did:

1. Launch terminal with Expert->Start root terminal
2. Enter "encfs" at the terminal command prompt

RESULT:
Got the encfs usage message. In other words, the linker error that I saw using the truecrypt binaries is not present with encfs.

Let me know if there are additional steps you want me to try.
I appreciate your help.

[neurodroid]

From christoph.schmidthieber@gmail.com on November 27, 2012 13:46:05

Thanks for your quick test. We'll have to wait for a reply from the Crystax team now.

[neurodroid]

From christoph.schmidthieber@gmail.com on November 27, 2012 18:40:56

This issue was closed by revision 63b3b33 .

Status: Fixed

[neurodroid]

From christoph.schmidthieber@gmail.com on November 27, 2012 19:08:15

Try the latest truecrypt binary, available from the downloads section: https://code.google.com/p/cryptonite/downloads/list

[neurodroid]

From anilkpa...@gmail.com on November 27, 2012 19:59:46

The new binary works. The linker error is gone. Thanks for the quick turnaround!
Now I have a different error with the mounting, but I can open another issue for that.

[neurodroid]

From christoph.schmidthieber@gmail.com on November 27, 2012 20:29:00

Yes please.

Status: FixVerified

[neurodroid]

From christoph.schmidthieber@gmail.com on November 28, 2012 06:11:52

Do you have a "mount" command sitting in /system/xbin/mount? If not, try to install BusyBox from the Play Store.

[neurodroid]

From anilkpa...@gmail.com on November 28, 2012 12:35:02

Yes, I have a mount command in /system/xbin/mount. This is linked to my busybox mount. The mount was failing because I had not created the target mount directory first. Once I did that, the mount succeeds. However, there is an issue with limited file accessibility. I've created issue #47 to describe it.

[neurodroid]

From christoph.schmidthieber@gmail.com on February 24, 2013 13:25:42

Issue 50 has been merged into this issue.