|
From: Mark R. <ma...@cs...> - 2018-01-02 16:49:26
|
I am having lots of problems getting Valgrind to run on Ubuntu 17.10 (on x86_64 hardware). First, valgrind/memcheck/tests/linux/stack_changes.c would not compile. I had to change the typedef on line 13 from ucontext to ucontext_t. But the larger, more pervasive problem is with this release of Ubuntu the gcc (7.2.0) compiler has changed to emitting position independent code by default. I have tried to add -no-pie to compiler options but have not been successful. Has anybody had these problems and/or have a solution? Thank you, Mark Roberts |
|
From: Tom H. <to...@co...> - 2018-01-02 17:06:18
|
On 02/01/18 16:20, Mark Roberts wrote: > But the larger, more pervasive problem is with this release of Ubuntu the gcc (7.2.0) compiler has changed to emitting position > independent code by default. I have tried to add -no-pie to compiler options but have not been successful. Why is that a problem? Fedora 27 uses gcc 7.2 as well and I have no trouble building valgrind there. Tom -- Tom Hughes (to...@co...) http://compton.nu/ |
|
From: John R. <jr...@bi...> - 2018-01-02 17:19:12
|
> But the larger, more pervasive problem is with this release of Ubuntu > the gcc (7.2.0) compiler has changed to emitting position > independent code by default. I have tried to add -no-pie > to compiler options but have not been successful. Why is that a problem? And is it a problem in building valgrind itself, or in applying an old valgrind to newly-compiled code? Please give an explicit example (copy+paste) of a new complaint, and analyze it as best you can. -- |