https://bugs.kde.org/show_bug.cgi?id=493301
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=447989
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=492422
--- Comment #24 from Mark Wielaard ---
(In reply to nilskemail+kde from comment #23)
> Quick note, not that I am just dumb: I only applied your most recent patch
> file "Implement stable variant of sync_file ioctls". Do I also need to a
https://bugs.kde.org/show_bug.cgi?id=492422
--- Comment #19 from Mark Wielaard ---
(In reply to nilskemail+kde from comment #18)
> I noticed a few other cases of valgrind reporting a duplicate close of
> dmabuf fds:
>
> ==727618== File descriptor 30: /dmabuf:727694-WPEWebProces
https://bugs.kde.org/show_bug.cgi?id=492422
--- Comment #17 from Mark Wielaard ---
Sorry, we are waiting for me to cleanup the DRM_IOCTL related ioctls.
I did the SYNC_IOC (sync_file) ioctls cleanly in the attachment to comment #15.
Just need to go over the DRM_IOCTL ioctrls to make sure we
https://bugs.kde.org/show_bug.cgi?id=492549
--- Comment #14 from Mark Wielaard ---
Very odd. On an almost identical Fedora 40 setup both ./a.out and valgrind -q
--tool=massif ./a.out simply return 0 (as they should) for the memchr example.
Could you run with valgrind -v and see which
https://bugs.kde.org/show_bug.cgi?id=492549
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #4 from Mark
https://bugs.kde.org/show_bug.cgi?id=492422
--- Comment #15 from Mark Wielaard ---
Created attachment 173179
--> https://bugs.kde.org/attachment.cgi?id=173179&action=edit
Implement stable variant of sync_file ioctls
We implemented an old staging android variant of the sync_file
ioct
https://bugs.kde.org/show_bug.cgi?id=492422
Mark Wielaard changed:
What|Removed |Added
Attachment #173151|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=492429
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #3 from Mark
https://bugs.kde.org/show_bug.cgi?id=492422
Mark Wielaard changed:
What|Removed |Added
Attachment #173148|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=492422
--- Comment #7 from Mark Wielaard ---
(In reply to Mark Wielaard from comment #6)
> Urgh, somehow the VKI_SYNC_IOC_MERGE macro in valgrind is broken/wrong.
O no. We got the constant and data structure definitions for sync_file from
some anci
https://bugs.kde.org/show_bug.cgi?id=492422
--- Comment #6 from Mark Wielaard ---
Urgh, somehow the VKI_SYNC_IOC_MERGE macro in valgrind is broken/wrong.
If you add this patch on top things should work.
Scratching my head now what we did wrong and why we need to hardcode the hex
value.
diff
https://bugs.kde.org/show_bug.cgi?id=492422
Mark Wielaard changed:
What|Removed |Added
Attachment #173142|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=492422
--- Comment #2 from Mark Wielaard ---
Created attachment 173142
--> https://bugs.kde.org/attachment.cgi?id=173142&action=edit
Quick and dirty record_fd_open for DRM_IOCTL_SYNCOBJ_HANDLE_TO_FD
Thanks for the report. I was unaware that the
https://bugs.kde.org/show_bug.cgi?id=492422
Mark Wielaard changed:
What|Removed |Added
CC||ahajk...@redhat.com
https://bugs.kde.org/show_bug.cgi?id=492214
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
CC
https://bugs.kde.org/show_bug.cgi?id=469782
--- Comment #7 from Mark Wielaard ---
(In reply to Mikhail Gorodetsky from comment #5)
> >
> > I think with GPLv2 they mean GPLv2-only, which would be incompatible with
> > GPLV2+ used by Valgrind.
> > So we would pick the BS
https://bugs.kde.org/show_bug.cgi?id=469782
--- Comment #6 from Mark Wielaard ---
(In reply to Mikhail Gorodetsky from comment #4)
> So, I need to
> * Clarify with zstd upstream why they use three slightly different licenses
Yes, we do know why, the code come from three different &quo
https://bugs.kde.org/show_bug.cgi?id=469782
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #3 from Mark
https://bugs.kde.org/show_bug.cgi?id=492125
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=478774
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=492125
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
See Also
https://bugs.kde.org/show_bug.cgi?id=492050
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=491667
--- Comment #3 from Mark Wielaard ---
And the following comment at the top:
/* KNOWN LIMITATIONS 2014-Nov-16
* Correctness: FMAXNM, FMINNM are implemented the same as FMAX/FMIN.
Also FP comparison "unordered" .. is implemented as
https://bugs.kde.org/show_bug.cgi?id=491667
--- Comment #2 from Mark Wielaard ---
Note that VEX/priv/guest_arm64_toIR.c contains the following comment:
/* --- 0x,0111: FMINNM d_d, s_s --- (FIXME KLUDGED) */
[...]
case BITS4(0,1,1,1): nm = "fminnm"; iop = mkVe
https://bugs.kde.org/show_bug.cgi?id=491667
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=491253
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=491253
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #1 from Mark
https://bugs.kde.org/show_bug.cgi?id=490651
--- Comment #11 from Mark Wielaard ---
(In reply to Philippe Waroquiers from comment #10)
> (In reply to Mark Wielaard from comment #9)
> > It is definitely noticeable for me. And I have seen much longer build times
> > on some no
https://bugs.kde.org/show_bug.cgi?id=319307
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=490651
--- Comment #9 from Mark Wielaard ---
Here are the timings on two of my machines (all on fresh checkouts)
= Intel Core i7-10850H
./autogen.sh && ./configure && time make -j8
real0m3.100s
user0m5.273s
sys 0m4.25
https://bugs.kde.org/show_bug.cgi?id=490651
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=490651
Mark Wielaard changed:
What|Removed |Added
Assignee|jsew...@acm.org |m...@klomp.org
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=490651
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
https://bugs.kde.org/show_bug.cgi?id=439082
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=383010
Mark Wielaard changed:
What|Removed |Added
CC||simon.fen...@imgtec.com
--- Comment #98 from
https://bugs.kde.org/show_bug.cgi?id=490009
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=489676
Mark Wielaard changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=317127
--- Comment #22 from Mark Wielaard ---
Created attachment 171372
--> https://bugs.kde.org/attachment.cgi?id=171372&action=edit
Avoid dev/inode check on btrfs with --sanity-level=3
With --sanity-level=3 or higher the aspacemgr sanity che
https://bugs.kde.org/show_bug.cgi?id=317127
--- Comment #21 from Mark Wielaard ---
Could we make it linux generic by just using __NR_statfs and struct statfs
(which seems defined for each linux arch already):
diff --git a/coregrind/m_aspacemgr/aspacemgr-linux.c
b/coregrind/m_aspacemgr/aspacemgr
https://bugs.kde.org/show_bug.cgi?id=489676
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|jsew...@acm.org
https://bugs.kde.org/show_bug.cgi?id=489676
Bug ID: 489676
Summary: vgdb handle EINTR and EAGAIN more consistently
Classification: Developer tools
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=317127
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=489221
--- Comment #5 from Mark Wielaard ---
This was implemented in:
commit 472b067e39a11a47ae3fa7cd7d3142558f78969d
Author: Julian Seward
Date: Sun Mar 17 21:41:42 2019 +0100
amd64: Implement RDRAND, VCVTPH2PS and VCVTPS2PH.
Bug 398870
https://bugs.kde.org/show_bug.cgi?id=489088
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=489088
--- Comment #12 from Mark Wielaard ---
commit 10a22445d747817932692b1c1ee3faa726121cb4
Author: Mark Wielaard
Date: Sun Jun 30 20:17:32 2024 +0200
Implement VMOVQ xmm1, xmm2/m64
We implemented the memory variant already, but not the reg
https://bugs.kde.org/show_bug.cgi?id=417572
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=391148
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=489088
Mark Wielaard changed:
What|Removed |Added
Assignee|jsew...@acm.org |m...@klomp.org
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=489088
--- Comment #8 from Mark Wielaard ---
So I think the implementation should be something like:
diff --git a/VEX/priv/guest_amd64_toIR.c b/VEX/priv/guest_amd64_toIR.c
index 28c37f092211..a7ea5951aac7 100644
--- a/VEX/priv/guest_amd64_toIR.c
+++ b/VEX
https://bugs.kde.org/show_bug.cgi?id=489221
Mark Wielaard changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=489221
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #1 from Mark
https://bugs.kde.org/show_bug.cgi?id=489088
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=417572
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=489088
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=391148
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=489088
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=489088
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #3 from Mark
https://bugs.kde.org/show_bug.cgi?id=487439
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=337388
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=331311
--- Comment #4 from Mark Wielaard ---
Note that the "test" program for bug
https://bugs.kde.org/show_bug.cgi?id=337388 makes use of this bug.
It would be nice if we could "virtualize" /proc/self/fd and /proc/self/fdinfo
But up
https://bugs.kde.org/show_bug.cgi?id=337388
--- Comment #2 from Mark Wielaard ---
Note that there is a bug in the example program:
fds = calloc(size, sizeof fds[0]);
if (fds != NULL) {
errnum = errno;
goto close_fds_dir;
}
should be if (fds == NULL)
--
You are
https://bugs.kde.org/show_bug.cgi?id=479661
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=488379
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=311655
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=202770
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=479661
--- Comment #4 from Mark Wielaard ---
Created attachment 170562
--> https://bugs.kde.org/attachment.cgi?id=170562&action=edit
Close both internal pipe fds after VG_(fork) in parent and child
Close both internal pipe fds after VG_(fork) in par
https://bugs.kde.org/show_bug.cgi?id=488379
--- Comment #3 from Mark Wielaard ---
Created attachment 170559
--> https://bugs.kde.org/attachment.cgi?id=170559&action=edit
Don't leave fds created with --log-file, --xml-file or --log-socket open
Don't leave fds created with
https://bugs.kde.org/show_bug.cgi?id=488441
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=202770
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
See Also
https://bugs.kde.org/show_bug.cgi?id=202770
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=488379
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=311655
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=479661
--- Comment #3 from Mark Wielaard ---
I don't think it was the commit 0432ce ("vgdb: implement the extended-remote
protocol") which seems to use CLOSEXEC correctly.
It seems to be related to the pipe created for debuginfod support
https://bugs.kde.org/show_bug.cgi?id=479661
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=488379
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=311655
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=402833
--- Comment #20 from Mark Wielaard ---
(In reply to Paul Floyd from comment #19)
> (In reply to Olly Betts from comment #18)
> > $ nm -D /usr/lib/x86_64-linux-gnu/libc.so.6|grep 00119f80
> > 00119f80 i __memcpy_c
https://bugs.kde.org/show_bug.cgi?id=488379
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=487862
--- Comment #9 from Mark Wielaard ---
Hi John,
(In reply to John Reiser from comment #8)
> What has changed is very large apps such as qemu-user-* which depend on
> dozens of "random" libraries, and the system
> builders/maintai
https://bugs.kde.org/show_bug.cgi?id=487862
--- Comment #6 from Mark Wielaard ---
BTW it seems this whole discussion is duplicated in the comments of
memcheck/mc_main.c mc_post_clo_init ()
// We assume that brk()/sbrk() does not initialise new memory. ...
With as conclusion:
// So we
https://bugs.kde.org/show_bug.cgi?id=487862
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #4 from Mark
https://bugs.kde.org/show_bug.cgi?id=487439
--- Comment #10 from Mark Wielaard ---
(In reply to Paul Floyd from comment #9)
> diff --git a/VEX/priv/guest_amd64_toIR.c b/VEX/priv/guest_amd64_toIR.c
> index f0b1c5516..28c37f092 100644
> --- a/VEX/priv/guest_amd64_toIR.c
> ++
https://bugs.kde.org/show_bug.cgi?id=487439
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #8 from Mark
https://bugs.kde.org/show_bug.cgi?id=487296
--- Comment #3 from Mark Wielaard ---
For each inherited fd VG_(init_preopened_fds) calls
ML_(record_fd_open_named)(-1, fd);
So the ThreadId will be -1. Which ML_(record_fd_open_with_given_name) documents
as
"If the tid is -1, this indicat
https://bugs.kde.org/show_bug.cgi?id=487296
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=487296
--- Comment #1 from Mark Wielaard ---
Nice. Thanks for catching this.
Yeah, it makes sense to start "tracking" std fds once they are closed (and
reopened).
One thought I had was that maybe this shouldn't be special cased for just
stdin
https://bugs.kde.org/show_bug.cgi?id=487296
Mark Wielaard changed:
What|Removed |Added
CC||ahajk...@redhat.com
https://bugs.kde.org/show_bug.cgi?id=317127
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #18 from Mark
https://bugs.kde.org/show_bug.cgi?id=486180
Mark Wielaard changed:
What|Removed |Added
CC||ar...@linux.ibm.com
--- Comment #7 from Mark
https://bugs.kde.org/show_bug.cgi?id=486293
Bug ID: 486293
Summary: memccpy false positives
Classification: Developer tools
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=486180
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=362680
Mark Wielaard changed:
What|Removed |Added
CC||v...@altlinux.org
--- Comment #6 from Mark
https://bugs.kde.org/show_bug.cgi?id=482358
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=485924
--- Comment #3 from Mark Wielaard ---
So the only tricky part is that we want to mimic this part of the (generic)
PRE(sys_kill):
/* If we're sending SIGKILL, check to see if the target is one of
our threads and handle it spec
https://bugs.kde.org/show_bug.cgi?id=485924
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=485778
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=485778
Mark Wielaard changed:
What|Removed |Added
Attachment #168679|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=485778
--- Comment #2 from Mark Wielaard ---
Created attachment 168679
--> https://bugs.kde.org/attachment.cgi?id=168679&action=edit
core errors gensuppressions support
Initial implementation for --gen-suppressions support for core errors
With t
1 - 100 of 1003 matches
Mail list logo
