https://bugs.kde.org/show_bug.cgi?id=452058
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #1 from Mark
https://bugs.kde.org/show_bug.cgi?id=450962
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=450962
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=352130
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=445211
--- Comment #13 from Mark Wielaard ---
Thanks, it works fine now with the new search paths. Pushed as:
commit 2c0fb665699309e1e02a02084324748f46a6c788
Author: Randy MacLeod
Date: Tue Oct 16 21:01:04 2018 -0400
Fix out of tree builds
https://bugs.kde.org/show_bug.cgi?id=445211
--- Comment #12 from Mark Wielaard ---
So we were missing a few more search path, but the following seems to make
document generation work again with srcdir != builddir
--- a/docs/Makefile.am
+++ b/docs/Makefile.am
@@ -124,11 +124,12 @@ LOGFILE
https://bugs.kde.org/show_bug.cgi?id=445211
--- Comment #11 from Mark Wielaard ---
(In reply to Mark Wielaard from comment #10)
> I also got an issue with the generated vg-entities.xml.
> But this was solved by running autoreconf -f instead of ./autogen.sh which I
> don't fully understa
https://bugs.kde.org/show_bug.cgi?id=445211
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=445011
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=450437
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=451878
--- Comment #2 from Mark Wielaard ---
Looks like my email about this to your @outlook.com address bounced. So just in
case you didn't see it:
Thanks, that applied fine. And I admit having been confused by memfd_create vs
memfd_secret before. I
have
https://bugs.kde.org/show_bug.cgi?id=450437
--- Comment #8 from Mark Wielaard ---
commit 8eb547054a051a00742b1b9e1b381015fafeacb9
Author: Mark Wielaard
Date: Wed Feb 16 22:56:31 2022 +0100
Warn for execve syscall with argv or argv[0] being NULL.
For execve valgrind would silently
https://bugs.kde.org/show_bug.cgi?id=450437
--- Comment #6 from Mark Wielaard ---
So do I assume correctly that the generic none/tests/execve,
memcheck/tests/execve1 and memchck/tests/execve2 tests PASS with this patch on
freebsd, but that the freebsd specific memcheck/tests/freebsd
https://bugs.kde.org/show_bug.cgi?id=450437
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=451878
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=451827
Mark Wielaard changed:
What|Removed |Added
CC||c...@us.ibm.com
https://bugs.kde.org/show_bug.cgi?id=451626
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=451626
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|jsew...@acm.org
https://bugs.kde.org/show_bug.cgi?id=451626
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #1 from Mark
https://bugs.kde.org/show_bug.cgi?id=434057
--- Comment #5 from Mark Wielaard ---
(In reply to Mark Wielaard from comment #4)
> This is only half of the work though. Although you can change the way gdb
> and vgdb communicate (it doesn't need to be through stdio, but we could also
> add
https://bugs.kde.org/show_bug.cgi?id=434057
--- Comment #4 from Mark Wielaard ---
We have been looking at this and for the valgrind side it would involve
something like Pedro suggests in comment #3. So vgdb would intercept the
extended-remote packages (which aren't currently implemented
https://bugs.kde.org/show_bug.cgi?id=445916
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=450437
Bug ID: 450437
Summary: Warn for execve syscall with argv or argv[0] being
NULL.
Product: valgrind
Version: 3.18.1
Platform: Other
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=413330
Mark Wielaard changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=449494
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=449494
--- Comment #3 from Mark Wielaard ---
(In reply to Mark Wielaard from comment #2)
> BTW. It turns out qemu doesn't do atomics, but does doe rdm:
> https://www.qemu.org/docs/master/system/arm/emulation.html
>
> Which is why you see rdm wit
https://bugs.kde.org/show_bug.cgi?id=444552
Mark Wielaard changed:
What|Removed |Added
CC||fwei...@redhat.com
--- Comment #4 from Mark
https://bugs.kde.org/show_bug.cgi?id=449838
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=449494
--- Comment #2 from Mark Wielaard ---
BTW. It turns out qemu doesn't do atomics, but does doe rdm:
https://www.qemu.org/docs/master/system/arm/emulation.html
Which is why you see rdm without atomics when running under qemu.
I think this is a valid
https://bugs.kde.org/show_bug.cgi?id=449838
--- Comment #5 from Mark Wielaard ---
(In reply to Daniele from comment #4)
> yes with--track-fds=no valgrind not crash
>
> for reproduce you need only to call io_uring_queue_init()
> https://pastebin.com/MzFxQGmb
Thanks. I think
https://bugs.kde.org/show_bug.cgi?id=449838
--- Comment #3 from Mark Wielaard ---
(In reply to Daniele from comment #2)
> isolate bug need time, but can try
>
> --trace-syscalls=yes
> LOG
> [...]
> SYSCALL[7498,1](425) sys_io_uring_setup ( 0x1000, 137422177456 )[sync] -->
https://bugs.kde.org/show_bug.cgi?id=449838
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #1 from Mark
https://bugs.kde.org/show_bug.cgi?id=434057
Mark Wielaard changed:
What|Removed |Added
CC||ahajk...@redhat.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=449672
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=413330
Mark Wielaard changed:
What|Removed |Added
CC||jch...@redhat.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=413330
Mark Wielaard changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Assignee|jsew...@acm.org
https://bugs.kde.org/show_bug.cgi?id=449672
Bug ID: 449672
Summary: ppc64 --track-origins=yes causes failures because of
bad cmov addHRegUse
Product: valgrind
Version: 3.18.1
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=449494
--- Comment #1 from Mark Wielaard ---
Got access to a QEMU vm which has:
processor : 0
BogoMIPS: 40.00
Features: fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid asimdrdm
CPU implementer : 0x51
CPU architecture: 8
CPU variant
https://bugs.kde.org/show_bug.cgi?id=449494
Bug ID: 449494
Summary: arm64: Mismatch detected between RDMA and atomics
features
Product: valgrind
Version: 3.18.1
Platform: Other
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=447386
Mark Wielaard changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=416753
--- Comment #7 from Mark Wielaard ---
*** Bug 447386 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=445011
Mark Wielaard changed:
What|Removed |Added
Summary|SIGCHLD is sent when|SIGCHLD is sent when
https://bugs.kde.org/show_bug.cgi?id=447991
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=447991
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=429424
--- Comment #4 from Mark Wielaard ---
(In reply to Oliver Kellogg from comment #3)
> I tried again with valgrind-3.17.0 on Tumbleweed 20211012 and the messages
> are different:
>
> > valgrind ./umbrello/umbrello5
> == Memcheck, a mem
https://bugs.kde.org/show_bug.cgi?id=416753
Mark Wielaard changed:
What|Removed |Added
CC||derp...@gmail.com
--- Comment #6 from Mark
https://bugs.kde.org/show_bug.cgi?id=447386
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=405377
--- Comment #5 from Mark Wielaard ---
For now I pushed the ENOSYS patch to make sure things just work with the new
glibc.
commit 1024237358f01009fe233cb1294f3b8211304eaa
Author: Mark Wielaard
Date: Fri Dec 10 17:41:59 2021 +0100
Implement
https://bugs.kde.org/show_bug.cgi?id=81
--- Comment #5 from Mark Wielaard ---
Thanks. Tests look good.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405377
--- Comment #3 from Mark Wielaard ---
Created attachment 144436
--> https://bugs.kde.org/attachment.cgi?id=144436=edit
implement rseq as ENOSYS
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405377
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=445916
--- Comment #4 from Mark Wielaard ---
Posted a patch to libiberty upstream:
https://gcc.gnu.org/pipermail/gcc-patches/2021-December/586058.html
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=446251
Bug ID: 446251
Summary: TARGET_SIGNAL_THR added to enum target_signal
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=434849
Mark Wielaard changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=446123
Mark Wielaard changed:
What|Removed |Added
CC||tul...@quites.com.br
--- Comment #1 from Mark
https://bugs.kde.org/show_bug.cgi?id=445916
--- Comment #3 from Mark Wielaard ---
(In reply to Nick Nethercote from comment #1)
> AFAIK Valgrind uses the libiberty demangler. How does that work? Is there
> scope for a Valgrind-specific fix, or would it be better to get the suffix
>
https://bugs.kde.org/show_bug.cgi?id=445668
--- Comment #9 from Mark Wielaard ---
(In reply to Nick Nethercote from comment #8)
> > The Rust compiler currently sometimes generates symbols with a
> > `.llvm.` suffix. These violate the v0 spec, which doesn't allow '.'
> > chars,
https://bugs.kde.org/show_bug.cgi?id=445668
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=445668
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=445916
Bug ID: 445916
Summary: Demangle Rust v0 symbols with .llvm suffix
Product: valgrind
Version: 3.19 GIT
Platform: Other
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=445668
--- Comment #11 from Mark Wielaard ---
(In reply to Nick Nethercote from comment #8)
> > The Rust compiler currently sometimes generates symbols with a
> > `.llvm.` suffix. These violate the v0 spec, which doesn't allow '.'
> > chars,
https://bugs.kde.org/show_bug.cgi?id=445668
--- Comment #6 from Mark Wielaard ---
I think I found it. rustc puts concrete function instances in namespaces (which
is allowed in DWARF since there is no strict separation between type
declarations and program scope entries in a DIE tree), the inline
https://bugs.kde.org/show_bug.cgi?id=445668
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=445668
--- Comment #1 from Mark Wielaard ---
(In reply to Nick Nethercote from comment #0)
> Here is some DHAT output I am getting with Rust code:
>
> > └── PP 1.14/14 {
> > Total: 118,312 bytes (0.05%, 60.74/Minstr) in 11,864
https://bugs.kde.org/show_bug.cgi?id=444925
--- Comment #3 from Mark Wielaard ---
The attached patch is reversed, but looking with patch -p1 -R it seems OK.
Some nitpicks:
- priv_syswrap-generic.h handle_sys_pwritev, please rename the argument
is_execveType -> execveType.
- Sho
https://bugs.kde.org/show_bug.cgi?id=445184
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
https://bugs.kde.org/show_bug.cgi?id=445011
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #5 from Mark
https://bugs.kde.org/show_bug.cgi?id=444831
Bug ID: 444831
Summary: vbit-test F16 Iops are tested on the wrong
architectures
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=444571
--- Comment #15 from Mark Wielaard ---
(In reply to Carl Love from comment #13)
> Mark, give the patch a spin and see if it works for you.
You patch fixes the following 4 tests:
-memcheck/tests/badrw (stderr)
-memcheck/tests/li
https://bugs.kde.org/show_bug.cgi?id=31
--- Comment #6 from Mark Wielaard ---
It would be really helpful if you could show the actual code. It really looks
like you are passing around some undefined values. You can also try adding
--track-origins=yes to see where the undefined values
https://bugs.kde.org/show_bug.cgi?id=444571
--- Comment #11 from Mark Wielaard ---
yeah, the fedora 35 gcc generates:
6 char x = a[-1];
0x171c <+48>:ld r9,32(r31)
0x1720 <+52>:lbz r9,-1(r9)
0x1724 <+56>:
https://bugs.kde.org/show_bug.cgi?id=444571
--- Comment #9 from Mark Wielaard ---
(In reply to Mark Wielaard from comment #8)
> (In reply to Carl Love from comment #7)
> > I have access to a Fedora system with gcc (GCC) 11.2.1 20210728 (Red Hat
> > 11.2.1-1) and glib 2.33.
>
https://bugs.kde.org/show_bug.cgi?id=444571
--- Comment #8 from Mark Wielaard ---
(In reply to Carl Love from comment #7)
> I have access to a Fedora system with gcc (GCC) 11.2.1 20210728 (Red Hat
> 11.2.1-1) and glib 2.33.
>
> When I try to run the binary b I get the message:
>
https://bugs.kde.org/show_bug.cgi?id=444571
--- Comment #6 from Mark Wielaard ---
(In reply to Mark Wielaard from comment #5)
> (In reply to Carl Love from comment #4)
> > Can you give me some info on your test environment? I have run the
> > regression tests (make regtes
https://bugs.kde.org/show_bug.cgi?id=444571
--- Comment #5 from Mark Wielaard ---
(In reply to Carl Love from comment #4)
> Can you give me some info on your test environment? I have run the
> regression tests (make regtest) on a Power 9 and a Power 10 system and don't
> see the
https://bugs.kde.org/show_bug.cgi?id=444571
--- Comment #3 from Mark Wielaard ---
There is also the following failure in memcheck/tests/badrw
--- badrw.stderr.exp2021-10-28 17:52:34.577616207 -0400
+++ badrw.stderr.out2021-10-28 17:57:16.957629621 -0400
@@ -10,24 +10,12 @@
at 0x
https://bugs.kde.org/show_bug.cgi?id=444571
--- Comment #2 from Mark Wielaard ---
I wonder if this is also related to the following fail in
helgrind/tests/free_is_write:
-ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 5 errors from 1 contexts (suppressed: 0 from
https://bugs.kde.org/show_bug.cgi?id=444571
Mark Wielaard changed:
What|Removed |Added
CC||will_schm...@vnet.ibm.com
--
You
https://bugs.kde.org/show_bug.cgi?id=444552
--- Comment #1 from Mark Wielaard ---
Note the following in glibc sysdeps/unix/sysv/linux/s390/ipc_priv.h:
/* The s390 sys_ipc variant has only five parameters instead of six
(as for default variant). The difference is the handling
https://bugs.kde.org/show_bug.cgi?id=444571
--- Comment #1 from Mark Wielaard ---
Created attachment 142985
--> https://bugs.kde.org/attachment.cgi?id=142985=edit
Example binary b
This is the ppc64le binary for:
#include
int main ()
{
char *a = malloc (1);
char x = a[-1];
}
--
https://bugs.kde.org/show_bug.cgi?id=444571
Bug ID: 444571
Summary: ppc64le dlclose_leak fails (when lxsibzx is used)
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=444568
Bug ID: 444568
Summary: drd/tests/pth_barrier_thr_cr Number of concurrent
pthread_barrier_wait() calls exceeds the barrier count
Product: valgrind
Version: unspecified
Platform:
https://bugs.kde.org/show_bug.cgi?id=444552
Bug ID: 444552
Summary: memcheck/tests/sem fails on s390x with glibc 2.34
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=95
Bug ID: 95
Summary: dhat/tests/copy fails on s390x
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=435732
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=403802
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=88
Bug ID: 88
Summary: Use glibc.pthread.stack_cache_size tunable
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=87
Bug ID: 87
Summary: hginfo test detects an extra lock inside data symbol
"_rtld_local"
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=81
Bug 81 depends on bug 441474, which changed state.
Bug 441474 Summary: vgdb might eat all memory while waiting for sigstop
https://bugs.kde.org/show_bug.cgi?id=441474
What|Removed |Added
https://bugs.kde.org/show_bug.cgi?id=81
Mark Wielaard changed:
What|Removed |Added
Depends on||441474
See Also
https://bugs.kde.org/show_bug.cgi?id=441474
Mark Wielaard changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Blocks
https://bugs.kde.org/show_bug.cgi?id=81
Bug ID: 81
Summary: gdb_server test failures on s390x
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=444278
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #2 from Mark
https://bugs.kde.org/show_bug.cgi?id=441936
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=441474
--- Comment #3 from Mark Wielaard ---
I pushed the workaround:
commit 970820852e542506dd7a4c722fecd73e34363fde
Author: Mark Wielaard
Date: Tue Oct 12 23:25:32 2021 +0200
vgdb: only queue up to 64 pending signals when waiting for SIGSTOP
https://bugs.kde.org/show_bug.cgi?id=426148
Mark Wielaard changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=439090
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=443605
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=439090
Mark Wielaard changed:
What|Removed |Added
Attachment #139634|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=439090
--- Comment #6 from Mark Wielaard ---
This is the diff on top of the original:
diff --git a/coregrind/m_syswrap/syswrap-linux.c
b/coregrind/m_syswrap/syswrap-linux.c
index 2840b3af0..63dd1fb66 100644
--- a/coregrind/m_syswrap/syswrap-linux.c
+++ b
301 - 400 of 1207 matches
Mail list logo
