https://bugs.kde.org/show_bug.cgi?id=497977
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=290061
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=339330
--- Comment #6 from Paul Floyd ---
I've long given up using suppressions.
I can't see how this can be fixed in Valgrind. There is instrumentation, but in
this case I think that it would need to be done within the standard library or
a
https://bugs.kde.org/show_bug.cgi?id=502263
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #1 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=420682
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=420682
--- Comment #5 from Paul Floyd ---
I've written a test for this and cleaned up the error messages a bit - there
were a few errors in the untested code.
Buildbot says I need to improve the configure.ac test the the syscall. There is
only the
https://bugs.kde.org/show_bug.cgi?id=420682
--- Comment #3 from Paul Floyd ---
Created attachment 179731
--> https://bugs.kde.org/attachment.cgi?id=179731&action=edit
initial patch
I haven't tested it yet properly, but could you try this patch?
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=420682
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=420682
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #2 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=501713
--- Comment #7 from Paul Floyd ---
Does the code run cleanly with Helgrind, DRD and TSAN?
This still looks like a thread issue to me and not a memcheck issue.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=486398
--- Comment #8 from Paul Floyd ---
The patch builds OK with no warnings on FreeBSD with clang 18.1.6. No problems
with the new tests either.
OK with sourceware build macines.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=501893
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=486398
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=501893
--- Comment #7 from Paul Floyd ---
Thanks for the examples. I can reproduce the issue. I'll push a fix and test
shortly.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=501893
--- Comment #3 from Paul Floyd ---
Created attachment 179659
--> https://bugs.kde.org/attachment.cgi?id=179659&action=edit
First go at a fix, based on strcmp.
Please could you test this patch?
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=501893
--- Comment #2 from Paul Floyd ---
Can you provide the two strings that generate this error?
On my PC with Fedora 41 wcscat is using __wcscat_evex. I don't know if that has
the same problem. That's glibc 2.40.
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=501893
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
Assignee|jsew
https://bugs.kde.org/show_bug.cgi?id=501850
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=501850
--- Comment #1 from Paul Floyd ---
I wrote a little test based on scalar
#include "scalar.h"
int main(void)
{
SY(SYS_sendfile, 1000, 2, 3, 4, 5, 6, 7, 8);
return(0);
}
I can comment out the sfMayBlock - the syscall will fail so no q
https://bugs.kde.org/show_bug.cgi?id=501850
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=501850
Bug ID: 501850
Summary: FreeBSD syscall arguments 7 and 8 incorrect.
Classification: Developer tools
Product: valgrind
Version: 3.25 GIT
Platform: Other
OS: FreeBSD
St
https://bugs.kde.org/show_bug.cgi?id=501846
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=501846
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=501846
Bug ID: 501846
Summary: Add x86 Linux shm wrappers
Classification: Developer tools
Product: valgrind
Version: 3.24 GIT
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=339330
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=501713
Paul Floyd changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=501713
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #2 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=501365
--- Comment #10 from Paul Floyd ---
(In reply to mcermak from comment #9)
> > Yes please, this code is simple enough
>
> Mark, is it really only about "hooking" the existing PRE() and POST() up?
> I've noticed that f
https://bugs.kde.org/show_bug.cgi?id=501479
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=234814
--- Comment #5 from Paul Floyd ---
Need to look at this again.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=501479
--- Comment #2 from Paul Floyd ---
There is a bug in Illumos pthread_mutexattr_gettype
See
https://github.com/illumos/illumos-gate/blob/master/usr/src/lib/libc/port/threads/pthr_mutex.c#L370
It just reads an uninit local variable which gets
https://bugs.kde.org/show_bug.cgi?id=501479
--- Comment #1 from Paul Floyd ---
Looking at this call
pthread_mutex_init(&mutex, &mutexattr);
The type for OI and Solaris 11.4 the same but different. OI is 8 (DEFAULT) and
S11.4 is 0 (DEFAULT and NORMAL). We treat both of these the sam
https://bugs.kde.org/show_bug.cgi?id=501479
Paul Floyd changed:
What|Removed |Added
Assignee|bart.vanassche+...@gmail.co |pjfl...@wanadoo.fr
|m
https://bugs.kde.org/show_bug.cgi?id=501479
Bug ID: 501479
Summary: Illumos DRD pthread_mutex_init wrapper errors
Classification: Developer tools
Product: valgrind
Version: 3.24 GIT
Platform: Compiled Sources
OS: Unspecifie
https://bugs.kde.org/show_bug.cgi?id=501365
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #3 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=501348
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=501194
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=234814
--- Comment #6 from Paul Floyd ---
(In reply to Paul Floyd from comment #5)
> Need to look at this again.
Works fine on FreeBSD. I need to go through my git history between 2020-04-13
(when it wasn't working on FreeBSD) and 2021-10-03 (whe
https://bugs.kde.org/show_bug.cgi?id=501194
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=501194
Bug ID: 501194
Summary: Fix ML_(check_macho_and_get_rw_loads) so that it is
correct for any number of segment commands
Classification: Developer tools
Product: valgrind
Version: 3.24 GI
https://bugs.kde.org/show_bug.cgi?id=271582
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=339160
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=271582
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #2 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=486398
--- Comment #5 from Paul Floyd ---
Thanks for the patch. I'm busy at the moment setting up a new PC. It might take
some time. I'll take a look when that's all done.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=496370
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=496370
--- Comment #5 from Paul Floyd ---
I'll try
#pragma GCC push_options
#pragma GCC optimize ("O0")
void VG_(save_context)(ThreadId tid, vki_ucontext_t *uc, CorePart part)
...
#pragma GCC pop_options
--
You are receiving this mail b
https://bugs.kde.org/show_bug.cgi?id=496370
--- Comment #4 from Paul Floyd ---
I've tried a GCC 12 build of Valgrind with both a GCC 4.8.2 and GCC 12 built
versions of signal2 and they both crash. So it's not a change in the
compilation of the testcase that's the problem.
Next, i
https://bugs.kde.org/show_bug.cgi?id=396415
--- Comment #15 from Paul Floyd ---
(In reply to Geoffrey Thomas from comment #14)
> Compiled from Git and it appears to work the way I expect on Linux. Thanks!
>
> # ../valgrind/vg-in-place --tool=none -q ./script
> Hello world!
Just
https://bugs.kde.org/show_bug.cgi?id=396415
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=396415
--- Comment #12 from Paul Floyd ---
Created attachment 178008
--> https://bugs.kde.org/attachment.cgi?id=178008&action=edit
Patch for Linux
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=396415
--- Comment #11 from Paul Floyd ---
After a bit of trying to battle with load_client() where we were VG_(open)'ing
"exe_name" (which could be a script with/without a shebang, and the shebang
could refer to another script [which could rep
https://bugs.kde.org/show_bug.cgi?id=499561
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #1 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=396415
--- Comment #10 from Paul Floyd ---
And fixing AT_EXECFN doesn't help on Linux (though we should probably do that
one day).
I think that we need to resolve the linked path before opening VG_(cl_exec_fd).
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=396415
--- Comment #9 from Paul Floyd ---
Created attachment 177987
--> https://bugs.kde.org/attachment.cgi?id=177987&action=edit
Patch for FreeBSD
Initial patch for FrfeeBSD. I also have a test (based on the existing auxv
test), not included in thi
https://bugs.kde.org/show_bug.cgi?id=396415
--- Comment #8 from Paul Floyd ---
Looking some more, on FreeBSD t looks like we're setting AT_EXECPATH to the
script name as follows
const HChar *exe_name = VG_(find_executable)(VG_(args_the_exename));
HChar resolved_name[VKI_PATH_MAX];
https://bugs.kde.org/show_bug.cgi?id=396415
--- Comment #7 from Paul Floyd ---
Just had a quick look on FreeBSD. It looks like it's just using __realpathat on
/path/link/main which, being a link, resolves to /path/orig/main, and then
getdirentries. Under Valgrind it's calling _rea
https://bugs.kde.org/show_bug.cgi?id=396415
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=496972
--- Comment #1 from Paul Floyd ---
The first error happens very early on.
Running under vgdb and using step-instruction to get back somewhere with a
stack
#0 0x08523e0d in ?? () from /usr/local/lib/libpcre2-16.so.0
#1 0x08523d46 in
https://bugs.kde.org/show_bug.cgi?id=396415
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #5 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=471802
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #21 from Paul
https://bugs.kde.org/show_bug.cgi?id=499183
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=499183
--- Comment #2 from Paul Floyd ---
I think that I see the problem.
GEN_test_RandM(VMOVQ_XMM_to_XMM_LOW_LOW_HIGH,
"vmovq %%xmm0, %%xmm7; vmovq %%xmm8, %%xmm0",
"vmovq %%xmm0, (%%rsi); vmovq %%xmm9, %%xmm0&
https://bugs.kde.org/show_bug.cgi?id=499212
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=499212
Paul Floyd changed:
What|Removed |Added
Summary|mmap() with MAP_ALIGNED() |mmap() with MAP_ALIGNED
https://bugs.kde.org/show_bug.cgi?id=499212
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
Assignee|jsew
https://bugs.kde.org/show_bug.cgi?id=499183
Bug ID: 499183
Summary: FreeBSD: differences in avx-vmovq output
Classification: Developer tools
Product: valgrind
Version: 3.24 GIT
Platform: FreeBSD Ports
OS: FreeBSD
https://bugs.kde.org/show_bug.cgi?id=499183
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=499183
--- Comment #1 from Paul Floyd ---
paulf@green:~/test/valgrind/none/tests/amd64 $ cat avx-vmovq.stdout.diff
--- avx-vmovq.stdout.exp2025-01-26 16:09:27.689155000 +0100
+++ avx-vmovq.stdout.out2025-01-26 22:39:32.558711000 +0100
@@ -87,7
https://bugs.kde.org/show_bug.cgi?id=492678
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=492678
--- Comment #8 from Paul Floyd ---
OK, I modified the testcase to use timer_create/timer_delete and reproduced
both the error and the fix on Linux. I couldn't reproduce the error with
FreeBSD. I'll try to push a fix and 2 testcases th
https://bugs.kde.org/show_bug.cgi?id=498936
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=498936
--- Comment #3 from Paul Floyd ---
(In reply to Tavian Barnes from comment #2)
> --fair-sched=yes seems to work around it
OK, can we close this item?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492678
--- Comment #6 from Paul Floyd ---
(In reply to Tavian Barnes from comment #3)
> I think this should fix it:
>
> diff --git a/coregrind/m_syswrap/syswrap-linux.c
> b/coregrind/m_syswrap/syswrap-linux.c
> index e8978b5bc..83af91344
https://bugs.kde.org/show_bug.cgi?id=492678
--- Comment #5 from Paul Floyd ---
And on Fedora (same PC) I had to increase the timer period to reproduce the
problem. The same change PRE(sys_setitimer) also seems to fix it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=492678
--- Comment #4 from Paul Floyd ---
This works for me on FreeBSD
diff --git a/coregrind/m_syswrap/syswrap-freebsd.c
b/coregrind/m_syswrap/syswrap-freebsd.c
index d358c90eb..339724938 100644
--- a/coregrind/m_syswrap/syswrap-freebsd.c
+++ b/coregrind
https://bugs.kde.org/show_bug.cgi?id=492678
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=498936
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
Assignee|jsew
https://bugs.kde.org/show_bug.cgi?id=498492
Paul Floyd changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=498492
--- Comment #2 from Paul Floyd ---
GCC/Linux
1139 :
1139: 55 push %rbp
113a: 48 89 e5mov%rsp,%rbp
113d: 48 89 7d d8 mov%rdi,-0x28(%rbp)
1141
https://bugs.kde.org/show_bug.cgi?id=498492
--- Comment #1 from Paul Floyd ---
objdump -d:
00201750 :
201750: 55pushq %rbp
201751: 48 89 e5 movq%rsp, %rbp
201754: 48 89 7d f8 movq%rdi, -0x8(%rbp)
201758
https://bugs.kde.org/show_bug.cgi?id=498494
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=498494
--- Comment #2 from Paul Floyd ---
This was on a VirtualBox instance. I hadn't realized just how bad the VB
virtualization is on a modern amd64 PC.
CPU flags in VB
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca
https://bugs.kde.org/show_bug.cgi?id=498494
--- Comment #1 from Paul Floyd ---
Linux / GCC generates the same opcode. So this is more likely to be related to
something like
Bool VG_(machine_get_hwcaps)( void )
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=498494
Paul Floyd changed:
What|Removed |Added
Summary|illegal instructions with |illegal instructions with
|none
https://bugs.kde.org/show_bug.cgi?id=498494
Bug ID: 498494
Summary: illegal instructions with none/tests/amd64/rdseed and
rdrand on FreeBSD compiled with clang
Classification: Developer tools
Product: valgrind
Version: unspecifie
https://bugs.kde.org/show_bug.cgi?id=498494
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=498492
Bug ID: 498492
Summary: none/tests/amd64/lzcnt64 crashes on FreeBSD compiled
with clang
Classification: Developer tools
Product: valgrind
Version: unspecified
Platform: FreeBS
https://bugs.kde.org/show_bug.cgi?id=498492
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=498317
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=498317
Paul Floyd changed:
What|Removed |Added
Assignee|jsew...@acm.org |pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=498317
--- Comment #1 from Paul Floyd ---
Reproduced. I'll try to push a fix tomorrow (2025-01-07).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=498317
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=496972
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=496972
--- Comment #6 from Paul Floyd ---
No the i386 errors are unrelated. It's a bug in sljit (the jitter used by
pcre2). This patch fixes it:
https://github.com/zherczeg/sljit/commit/db3ca5014f0ae524785be05f071addc45a3442e0
If I correctly initi
https://bugs.kde.org/show_bug.cgi?id=496972
--- Comment #5 from Paul Floyd ---
I don't know if the i386 issue is the same thing.
The code is doing a 'cpuid' and then checking what is in eax. I can't see
anything wrong particularly. The pcre2 code looks similar to
none/tests
https://bugs.kde.org/show_bug.cgi?id=496972
--- Comment #4 from Paul Floyd ---
On FreeBSD i386
==33163== Conditional jump or move depends on uninitialised value(s)
==33163==at 0xEB46A34: get_cpu_features (sljitNativeX86_common.c:512)
==33163==by 0xEB46978: init_compiler
https://bugs.kde.org/show_bug.cgi?id=496972
--- Comment #3 from Paul Floyd ---
Started with arm (Raspberry Pi OS). No problem there. (Don't know if pcre2 uses
jitting on that platform).
No problem on arm64 either (Ubuntu and FreeBSD).
So just amd64.
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=496972
Paul Floyd changed:
What|Removed |Added
OS|FreeBSD |All
Platform|FreeBSD Ports
https://bugs.kde.org/show_bug.cgi?id=497977
--- Comment #15 from Paul Floyd ---
(In reply to Vincent Lefèvre from comment #14)
> This is still confusing, because with an unsigned size_t, a negative value
> is not possible.
> Or you should say: "possibly a negative value conve
https://bugs.kde.org/show_bug.cgi?id=497977
--- Comment #13 from Paul Floyd ---
(In reply to Vincent Lefèvre from comment #12)
> The issue is not the value itself, but the fact that valgrind currently says
> that the value is negative. This gives confusing information for the user.
&g
1 - 100 of 1316 matches
Mail list logo
