When I run statifier on a 32-bit executable it produces an executable that will run on a 32-bit system. However, the resultant executable segfaults when run on a 64-bit machine. Also, if I run statifier on a 64-bit version of the executable, the resulting executable segfaults when run.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Could you please provide a bit more info:
what is your 32-bit system (distribution, version, kernel version) where statified exe works
what is your 64-bit system (distribution, version, kernel version) where statified exe fails
Output of
cat /proc/self/maps
twice for each system
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As I said, four days ago the process would work on the 32-bit system, but not on my 64-bit system. Now, for some reason, it won't work on either system. I don't recall changing the code in the meanwhile.
Segmentation fault on any D-generated 64 bit executable. Minimal example attached. If you want to compile example itself you need DMD and dub (both exists in Ubuntu software repos).
Ubuntu 16.04 64 bit
Unfortunately, statifiied program segfault on the systems with memory randomization.
You can try to turn memory randomization off, statify your executable and then try to run it.
Valery
From:AlexeyKulentsov<crimaniak@users.sf.net>
To: [statifier:discussion]358807@discussion.statifier.p.re.sf.net
Sent: Wednesday, September 14, 2016 10:10 PM
Subject: [statifier:discussion] Segmentation fault on 64-bit system
Segmentation fault on any D-generated 64 bit executable. Minimal example attached. If you want to compile example itself you need DMD and dub (both exists in Ubuntu software repos).
Ubuntu 16.04 64 bitAttachments:
When I run statifier on a 32-bit executable it produces an executable that will run on a 32-bit system. However, the resultant executable segfaults when run on a 64-bit machine. Also, if I run statifier on a 64-bit version of the executable, the resulting executable segfaults when run.
Could you please provide a bit more info:
what is your 32-bit system (distribution, version, kernel version) where statified exe works
what is your 64-bit system (distribution, version, kernel version) where statified exe fails
Output of
cat /proc/self/maps
twice for each system
Well, I'm not sure what's changed, but now it doesn't work at all, even on the 32-bit system.
32-bit system: Debian 7.9 3.2.0-4-686-pae #1 SMP Debian 3.2.68-1+deb7u3 i686 GNU/Linux
64-bit system: Debian 8.2 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) x86_64 GNU/Linux
As I said, four days ago the process would work on the 32-bit system, but not on my 64-bit system. Now, for some reason, it won't work on either system. I don't recall changing the code in the meanwhile.
32-bit system:
64-bit system:
Last edit: Sod Almighty 2016-08-19
Incidentally:
Sigh :(
Segmentation fault on any D-generated 64 bit executable. Minimal example attached. If you want to compile example itself you need DMD and dub (both exists in Ubuntu software repos).
Ubuntu 16.04 64 bit
Unfortunately, statifiied program segfault on the systems with memory randomization.
You can try to turn memory randomization off, statify your executable and then try to run it.
Valery
To: [statifier:discussion] 358807@discussion.statifier.p.re.sf.net
Sent: Wednesday, September 14, 2016 10:10 PM
Subject: [statifier:discussion] Segmentation fault on 64-bit system
Segmentation fault on any D-generated 64 bit executable. Minimal example attached. If you want to compile example itself you need DMD and dub (both exists in Ubuntu software repos).
Ubuntu 16.04 64 bitAttachments:
Segmentation fault on 64-bit systemSent from sourceforge.net because you indicated interest in https://sourceforge.net/p/statifier/discussion/358807/To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/