|
From: Mark R. <ma...@cs...> - 2018-01-02 23:11:38
|
I'm so sorry - I left out some information and my message was not clear. Valgrind itself builds and runs fine it's the regression tests that failed to compile and/or link. During my further investigation, the pie/no-pie linking problem turned out to be a bad file in our repository. The problem with valgrind/memcheck/tests/linux/stack_changes.c appears to be an actual problem with the source. In June of 2017 the gnu c header file sys/ucontext.h was changed. typedef struct ucontext is now typedef struct ucontext_t. This change is included in the latest release of glibc 2.26 (Aug 2017). Thank you, Mark Roberts -----Original Message----- From: John Reiser [mailto:jr...@bi...] Sent: Tuesday, January 02, 2018 9:02 AM To: val...@li... Subject: Re: [Valgrind-users] problems with Ubuntu 17.10 > 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. -- ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Valgrind-users mailing list Val...@li... https://lists.sourceforge.net/lists/listinfo/valgrind-users |
|
From: Mark W. <ma...@kl...> - 2018-01-02 23:44:48
|
On Tue, Jan 02, 2018 at 02:39:36PM -0800, Mark Roberts wrote: > The problem with valgrind/memcheck/tests/linux/stack_changes.c appears > to be an actual problem with the source. In June of > 2017 the gnu c header file sys/ucontext.h was changed. > typedef struct ucontext is now typedef struct ucontext_t. This change > is included in the latest release of glibc 2.26 (Aug 2017). There is already a patch in git: https://sourceware.org/git/?p=valgrind.git;a=commitdiff;h=2b5eab6a8db1b0487a3ad7fc4e7eeda6d3513626;hp=02b719e7b2f4c88eedd8b5689d842a62118cb47a But no release yet. Cheers, Mark |
|
From: Mark R. <ma...@cs...> - 2018-01-05 17:36:22
|
This patch just changes the definition to the 2.26 version. What about older versions? Doesn't this change need to be dependent on a GLIBC_VERSION check in configure? -----Original Message----- From: Mark Wielaard [mailto:ma...@kl...] Sent: Tuesday, January 02, 2018 3:27 PM To: Mark Roberts Cc: 'John Reiser'; val...@li... Subject: Re: [Valgrind-users] problems with Ubuntu 17.10 On Tue, Jan 02, 2018 at 02:39:36PM -0800, Mark Roberts wrote: > The problem with valgrind/memcheck/tests/linux/stack_changes.c > appears to be an actual problem with the source. In June of > 2017 the gnu c header file sys/ucontext.h was changed. > typedef struct ucontext is now typedef struct ucontext_t. This change > is included in the latest release of glibc 2.26 (Aug 2017). There is already a patch in git: https://sourceware.org/git/?p=valgrind.git;a=commitdiff;h=2b5eab6a8db1b0487a3ad7fc4e7eeda6d3513626;hp=02b719e7b2f4c88eedd8b5689 d842a62118cb47a But no release yet. Cheers, Mark |
|
From: 'Mark W. <ma...@kl...> - 2018-01-05 18:42:03
|
On Fri, Jan 05, 2018 at 09:36:16AM -0800, Mark Roberts wrote: > On Tue, Jan 02, 2018 at 02:39:36PM -0800, Mark Roberts wrote: > > The problem with valgrind/memcheck/tests/linux/stack_changes.c > > appears to be an actual problem with the source. In June of > > 2017 the gnu c header file sys/ucontext.h was changed. > > typedef struct ucontext is now typedef struct ucontext_t. This change > > is included in the latest release of glibc 2.26 (Aug 2017). > > There is already a patch in git: > https://sourceware.org/git/?p=valgrind.git;a=commitdiff;h=2b5eab6a8db1b0487a3ad7fc4e7eeda6d3513626;hp=02b719e7b2f4c88eedd8b5689d842a62118cb47a > This patch just changes the definition to the 2.26 version. What about older versions? Doesn't this change need to be > dependent on a GLIBC_VERSION check in configure? No. ucontext_t works for older glibc versions too. Cheers, Mark |