https://bugs.kde.org/show_bug.cgi?id=372347
--- Comment #9 from Paul Floyd <pa...@free.fr> ---
Created attachment 102909
--> https://bugs.kde.org/attachment.cgi?id=102909=edit
Patch to add C++14 sized delete overloads
Tested on Solaris 32bit and 64bit, Linux 64 bit (don't currently h
https://bugs.kde.org/show_bug.cgi?id=372347
--- Comment #7 from Paul Floyd <pa...@free.fr> ---
Created attachment 102906
--> https://bugs.kde.org/attachment.cgi?id=102906=edit
Patch to add C++14 sized delete overloads
Tested on Solaris.
==9916== ERROR SUMMARY: 0 errors from 0
https://bugs.kde.org/show_bug.cgi?id=372347
Paul Floyd <pa...@free.fr> changed:
What|Removed |Added
Attachment #102906|0 |1
is ob
https://bugs.kde.org/show_bug.cgi?id=372347
Paul Floyd <pa...@free.fr> changed:
What|Removed |Added
CC||pa...@free.fr
--- Comment #
https://bugs.kde.org/show_bug.cgi?id=372347
Paul Floyd <pa...@free.fr> changed:
What|Removed |Added
Attachment #102909|0 |1
is ob
https://bugs.kde.org/show_bug.cgi?id=372347
--- Comment #10 from Paul Floyd <pa...@free.fr> ---
Created attachment 103028
--> https://bugs.kde.org/attachment.cgi?id=103028=edit
Patch for C++14 sized delete operators
Added operator[] overloads. Tested on Solaris 32 and 64bit, Linux
https://bugs.kde.org/show_bug.cgi?id=372347
--- Comment #12 from Paul Floyd <pa...@free.fr> ---
Are you having issues with C++14 or C++17? I have a patch for C++14. I need to
do a bit more work to get my regression tests for it into the Valgrind format.
For the C++17, it looks like a lo
https://bugs.kde.org/show_bug.cgi?id=372347
--- Comment #14 from Paul Floyd <pa...@free.fr> ---
Can you test the patch attached here?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372347
--- Comment #17 from Paul Floyd ---
Great. I also have a small test case for this, but it uses a Makefile rather
than the Valgrind perl mechanism. I'll look into adapting it to the Valgrind
infrastructure.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=372347
--- Comment #19 from Paul Floyd ---
I think that -fsized-deallocation would be better as it’s more specific.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=388787
--- Comment #2 from Paul Floyd ---
Testcase to reproduce this behaviour:
# Makefile
.PHONY: clean
# GCC and Valgrind built from SVN/git head
CXX=${HOME}/tools/gcc/bin/g++
VG=${HOME}/tools/valgrind/bin/valgrind
test32: test.cpp
${CXX} -o
https://bugs.kde.org/show_bug.cgi?id=388787
--- Comment #4 from Paul Floyd ---
This is starting to look good. I now get
--17711-- _ZnwmSt11align_val_t(size 64, al 64) = 0x5AB4CC0
--17711-- _ZdlPvSt11align_val_t(0x5AB4CC0)
--17711-- _ZnamSt11align_val_t(size 320, al 64) = 0x5AB4DC0
--17711
https://bugs.kde.org/show_bug.cgi?id=388787
--- Comment #5 from Paul Floyd ---
Created attachment 113074
--> https://bugs.kde.org/attachment.cgi?id=113074=edit
Patch adding aligned new delete support
A fairly big change as I added to the existing alloc/new functions and the
ALLOC mac
https://bugs.kde.org/show_bug.cgi?id=388787
--- Comment #3 from Paul Floyd ---
On Solaris the signatures are
32bit demangled
U operator delete[](void*, std::align_val_t)
U operator delete(void*, unsigned int, std::align_val_t)
U operator new[](unsigned int, std
https://bugs.kde.org/show_bug.cgi?id=390871
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--- Comment #1 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=390871
--- Comment #2 from Paul Floyd ---
Mail from Rainer Orth on GCC mailing list
those sections are in libstdc++.so. They can be found in the input
objects used to created libstdc++.so on Linux and Solaris alike, due to
the use of -fdata-sections (via
https://bugs.kde.org/show_bug.cgi?id=388787
Bug ID: 388787
Summary: Support for C++17 new/delete
Product: valgrind
Version: 3.14 SVN
Platform: Other
OS: All
Status: UNCONFIRMED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=388787
--- Comment #1 from Paul Floyd <pa...@free.fr> ---
The LLVM libcxx implementation of aligned new does the following:
void *
operator new(std::size_t size, std::align_val_t alignment) _THROW_BAD_ALLOC
{
set size to at least 1
set
https://bugs.kde.org/show_bug.cgi?id=407589
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--- Comment #4 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=407589
--- Comment #5 from Paul Floyd ---
A more authoritative reference
https://en.cppreference.com/w/c/memory/aligned_alloc
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=234814
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--- Comment #4 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=403212
Paul Floyd changed:
What|Removed |Added
Assignee|bvanass...@acm.org |pa...@free.fr
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=403212
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--- Comment #2 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=402985
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pa...@free.fr
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=402985
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=317581
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=214950
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=69530
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=319393
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=110240
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=110209
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=407589
--- Comment #7 from Paul Floyd ---
Created attachment 127060
--> https://bugs.kde.org/attachment.cgi?id=127060=edit
Patch for algned_alloc support
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=407589
--- Comment #8 from Paul Floyd ---
Finally, I did start writing some regression tests, for instance
// example from here https://en.cppreference.com/w/c/memory/aligned_alloc
#include
#include
int main(void)
{
int *p1 = malloc(10*sizeof *p1
https://bugs.kde.org/show_bug.cgi?id=407589
--- Comment #6 from Paul Floyd ---
I'll look at reallocarray another day on FreeBSD (not a high priority for me).
For aligned_alloc, I don't think that this will work well. The problem is that
aligned_alloc and and memalign alias the same function
https://bugs.kde.org/show_bug.cgi?id=407589
--- Comment #9 from Paul Floyd ---
Even more finally, this patch is worthwhile on FreeBSD.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=316903
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--- Comment #15 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=406681
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=413410
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=412745
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=208531
--- Comment #33 from Paul Floyd ---
Over 10 years since this item was opened and it's my turn to take a stab at
getting it done.
Here a couple of sample results (best and worst)
GCC on amd64 configured with -O0
== 714 tests, 19 stderr failures, 5
https://bugs.kde.org/show_bug.cgi?id=306235
Paul Floyd changed:
What|Removed |Added
Assignee|n...@valgrind.org|pa...@free.fr
CC
https://bugs.kde.org/show_bug.cgi?id=208531
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=388787
Paul Floyd changed:
What|Removed |Added
Attachment #113074|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=306235
Paul Floyd changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=402985
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=425445
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--- Comment #1 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=428004
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--- Comment #1 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=407589
--- Comment #10 from Paul Floyd ---
Currently, in practice I don't see much benefit in adding reallocarray.
The glibc implementation just uses realloc:
https://code.woboq.org/userspace/glibc/malloc/reallocarray.c.html
So does the FreeBSD
https://bugs.kde.org/show_bug.cgi?id=427510
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--- Comment #4 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=427433
--- Comment #6 from Paul Floyd ---
This is with the original testcase.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=414290
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=415393
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=388493
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=252600
Paul Floyd changed:
What|Removed |Added
Resolution|--- |UNMAINTAINED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=296166
Paul Floyd changed:
What|Removed |Added
Resolution|--- |UNMAINTAINED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=332591
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=306340
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
Resolution
https://bugs.kde.org/show_bug.cgi?id=335353
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=321681
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
Resolution
https://bugs.kde.org/show_bug.cgi?id=323777
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=215510
Paul Floyd changed:
What|Removed |Added
Resolution|--- |UNMAINTAINED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=306340
Paul Floyd changed:
What|Removed |Added
Resolution|UNMAINTAINED|---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=388493
Paul Floyd changed:
What|Removed |Added
Status|RESOLVED|REPORTED
Resolution|UNMAINTAINED
https://bugs.kde.org/show_bug.cgi?id=185801
Paul Floyd changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=335353
Paul Floyd changed:
What|Removed |Added
Resolution|UNMAINTAINED|---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=384729
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=427433
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--- Comment #4 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=208531
--- Comment #36 from Paul Floyd ---
Gory details, part 3. Last for the moment.
Good news for any FreeBSD users compiling with GCC on amd64:
== 735 tests, 7 stderr failures, 1 stdout failure, 0 stderrB failures, 0
stdoutB failures, 0 post failures
https://bugs.kde.org/show_bug.cgi?id=424018
Bug ID: 424018
Summary: Valgrind crashes with --trace-syscalls=yes if syscalls
use PRINT %s with a non-dereferenceable string
Product: valgrind
Version: unspecified
Platform:
https://bugs.kde.org/show_bug.cgi?id=208531
--- Comment #37 from Paul Floyd ---
clang/x86 none/tests/sigsusp no longer hangs :-)
That 'only' leaves a couple of segfaults and client requests with clang as
serious problems on FreeBSD 12.1.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=424034
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--- Comment #1 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=407589
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pa...@free.fr
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=170510
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--- Comment #2 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=208531
--- Comment #34 from Paul Floyd ---
Some gory details, part 1. In the FreeBSD world, normally there are 2 active
release streams (currently 11 and 12) and one development stream (currently
13). The system compiler is clang, with GCC as an optional
https://bugs.kde.org/show_bug.cgi?id=208531
--- Comment #35 from Paul Floyd ---
Gory details part 2.
x86/clang, this is the worst case.
== 668 tests, 32 stderr failures, 2 stdout failures, 3 stderrB failures, 1
stdoutB failure, 0 post failures ==
Mostly the same as amd64/clang
none/tests
https://bugs.kde.org/show_bug.cgi?id=424012
--- Comment #1 from Paul Floyd ---
Created attachment 129990
--> https://bugs.kde.org/attachment.cgi?id=129990=edit
Patch to solve the problem and update regtest + expected
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=424012
Bug ID: 424012
Summary: Valgrind crashes with readv/writev having invalid but
not NULL arg2 iovec pointer
Product: valgrind
Version: 3.15 SVN
Platform: Compiled Sources
https://bugs.kde.org/show_bug.cgi?id=424012
--- Comment #2 from Paul Floyd ---
With the attached patch
paulf> perl tests/vg_regtest memcheck/tests/writev1
writev1: valgrind -q ./writev1
== 1 test, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB
failures, 0 p
https://bugs.kde.org/show_bug.cgi?id=422715
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=264253
Paul Floyd changed:
What|Removed |Added
CC||pa...@free.fr
--- Comment #5 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=306235
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|ASSIGNED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=372347
--- Comment #20 from Paul Floyd ---
Created attachment 130196
--> https://bugs.kde.org/attachment.cgi?id=130196=edit
Patch to test this support
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398545
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=428909
--- Comment #17 from Paul Floyd ---
> Please change this into configure tests that verify whether pthreads
> functions exist in libpthread, libc or in both.
Hi Bart
That's a good idea, but the devil is in the details. I have two fairly big
que
https://bugs.kde.org/show_bug.cgi?id=408663
--- Comment #2 from Paul Floyd ---
Created attachment 133688
--> https://bugs.kde.org/attachment.cgi?id=133688=edit
Update suppression file
File taken from the Alpine package build
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=428909
Paul Floyd changed:
What|Removed |Added
Attachment #133507|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=396656
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=408663
--- Comment #1 from Paul Floyd ---
I was recently doing some build testing on Alpine Linux, so I'll add this one
to my todo list. It should be very straightforward.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408663
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=271615
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=428909
--- Comment #21 from Paul Floyd ---
(In reply to Mark Wielaard from comment #19)
> Shouldn't that first #if defined(VGO_darwin) in drd_pthread_intercepts.c be
> #if defined(VG_WRAP_THREAD_FUNCTION_LIBPTHREAD_ONLY) ?
>
> Otherwis
https://bugs.kde.org/show_bug.cgi?id=428909
--- Comment #22 from Paul Floyd ---
(In reply to Mark Wielaard from comment #20)
> I find the logic in the previous patch much easier to follow. The configure
> tests look complex/fragile. Also I am not sure the first
> ac_thread_fns_only_in
https://bugs.kde.org/show_bug.cgi?id=382083
--- Comment #1 from Paul Floyd ---
This diff seems to be more portable
diff --git a/configure.ac b/configure.ac
index b83787291..93b57504c 100755
--- a/configure.ac
+++ b/configure.ac
@@ -1085,7 +1085,7 @@ fi
# GLIBC_VERSION is empty if a musl libc
https://bugs.kde.org/show_bug.cgi?id=417264
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=429952
Paul Floyd changed:
What|Removed |Added
Attachment #133826|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=382083
--- Comment #3 from Paul Floyd ---
>From what I've seen on Alpine, the basic musl support is there (e.g., for
memcheck) but there are quite a few issues (regtest build failures, helgrind
totally broken).
The musl detection on Alpine seems
https://bugs.kde.org/show_bug.cgi?id=408663
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=428909
--- Comment #10 from Paul Floyd ---
I'll attempt to add as many explanations as possible.
First, the true nature of the problem on Fedora 33. For some very bizarre
reason, pthread_cond_destroy is no longer in libpthread:
paulf> nm /li
https://bugs.kde.org/show_bug.cgi?id=427433
Paul Floyd changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=395266
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #1 from Paul Floyd
1 - 100 of 1546 matches
Mail list logo
