valgrind-users

[Valgrind-users] problems with Ubuntu 17.10

[Mark R. <ma...@cs...>]

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

Re: [Valgrind-users] problems with Ubuntu 17.10

[Tom H. <to...@co...>]

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/

Re: [Valgrind-users] problems with Ubuntu 17.10

[John R. <jr...@bi...>]

> 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.

--