Makefile fails if g++-4.8 does not exist

[ldionmarcil]

Hey, is there any reason why g++-4.8 is being explicitly called in the Makefile? The readme says 4.8 and up, but I got gcc 4.9 and no g++-anything on my machine. Would simply calling g++ instead of g++-4.8 be enough?

Linux tower 3.15.4-1-ARCH #1 SMP PREEMPT Mon Jul 7 07:42:54 CEST 2014 x86_64 GNU/Linux

Thanks!

[ewimberley]

Sorry it took so long to respond. AddressSanitizer was introduced into the GCC compiler suite starting in 4.8, and at the time 4.8 wasn't installed any hardly any systems. When people did install it, the "g++" would still refer to the old version unless the user changed it. Since 4.8 is more common now, I will write a patch soon to just use "g++" in the Makefile. In the mean time, you should be able to either replace the lines in the Makefile with your specific version, or just use "g++" instead of "g++-4.8".

Note: I do not know what changed in glibc across g++ versions, nor do I know what PAX stuff has been implemented in your kernel. I doubt it will make much of a difference, but if malloc or new have been changed significantly it could change the way you write the exploit.

[ewimberley]

Fixed