https://bugs.kde.org/show_bug.cgi?id=414291
--- Comment #5 from Per Mildner ---
It is indeed a good outcome. Plain http is obsolete and Google Chrome, for
instance, shows such sites as "Not Secure", which is not a good first
impression.
So, perhaps the https version of the URL should
https://bugs.kde.org/show_bug.cgi?id=414291
--- Comment #3 from Per Mildner ---
It works now. Thanks.
(I did not see that URL advertised but I use https for everything, if at all
possible.)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=414291
Bug ID: 414291
Summary: https://valgrind.org has an invalid certificate
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severit
https://bugs.kde.org/show_bug.cgi?id=414290
Bug ID: 414290
Summary: Release notes are corrupted on valgrind.org
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: n
https://bugs.kde.org/show_bug.cgi?id=379893
--- Comment #6 from Per Mildner ---
I did try valgrind --tool=lackey myprogram with todays git
(2b0aa0a5b88f900e986a3360952fcb3d2513419d) on macOS 10.13.6 and it crashes
with:
==73034== Process terminating with default action of signal 11 (SIGSEGV
https://bugs.kde.org/show_bug.cgi?id=379893
--- Comment #5 from Per Mildner ---
I am unsure exactly which patch to apply, and to which version of valgrind.
Is there a git branch I could try instead?
Also, I am now using macOS 10.13.6, so it is more interesting for me whether it
works there. I
https://bugs.kde.org/show_bug.cgi?id=349128
Per Mildner changed:
What|Removed |Added
CC||per.mild...@sics.se
--- Comment #4 from Per
https://bugs.kde.org/show_bug.cgi?id=379893
--- Comment #3 from Per Mildner ---
The behavior is similar with todays valgrind (built with Xcode 8.3.3):
-bash$ svn log | head -10
r16450 | mjw | 2017-06-16 11:33:35 +0200 (Fri
https://bugs.kde.org/show_bug.cgi?id=379893
--- Comment #2 from Per Mildner ---
valgrind itself segfaults when I run it with my program as argument. This also
happens with --tool=lackey.
valgrind successfully runs when passed "ls", so it is not completely broken.
svn log says:
r1638
https://bugs.kde.org/show_bug.cgi?id=379893
--- Comment #1 from Per Mildner ---
Created attachment 105587
--> https://bugs.kde.org/attachment.cgi?id=105587&action=edit
OS X Problem Report details
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=379893
Bug ID: 379893
Summary: valgrind segfault os x 10.12.4
Product: valgrind
Version: unspecified
Platform: Compiled Sources
OS: OS X
Status: UNCONFIRMED
Severity: n
https://bugs.kde.org/show_bug.cgi?id=361351
Per Mildner changed:
What|Removed |Added
CC||per.mild...@sics.se
--
You are receiving this
12 matches
Mail list logo