https://bugs.kde.org/show_bug.cgi?id=303877
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--- Comment #10 from Mark Wiela
https://bugs.kde.org/show_bug.cgi?id=303877
--- Comment #12 from Mark Wielaard ---
(In reply to Роман Донченко from comment #11)
> (In reply to Mark Wielaard from comment #10)
> > Debian does not seems to use GNU .zdebug compression,
>
> It does, though not for all packages yet. Here's an exampl
https://bugs.kde.org/show_bug.cgi?id=323431
Mark Wielaard changed:
What|Removed |Added
Summary|VEX: unhandled instruction |Unhandled AMD XOP
|bytevex am
https://bugs.kde.org/show_bug.cgi?id=357873
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=353370
Mark Wielaard changed:
What|Removed |Added
CC||miabr...@gmail.com
--- Comment #12 from Mark Wi
https://bugs.kde.org/show_bug.cgi?id=358030
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--- Comment #4 from Mark Wielaa
https://bugs.kde.org/show_bug.cgi?id=358213
--- Comment #1 from Mark Wielaard ---
Created attachment 96738
--> https://bugs.kde.org/attachment.cgi?id=96738&action=edit
pthread_barrier-vs-newer-glibc-implementation
These changes make the bar_bad testcase PASS against both the old and new
implem
https://bugs.kde.org/show_bug.cgi?id=358213
Bug ID: 358213
Summary: helgrind bar_bad testcase hangs with new glibc pthread
barrier implementation
Product: valgrind
Version: 3.11 SVN
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=357833
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--- Comment #3 from Mark Wielaa
https://bugs.kde.org/show_bug.cgi?id=357833
--- Comment #4 from Mark Wielaard ---
Replicated it now with the fedora rawhide kernel
4.5.0-0.rc0.git6.1.fc24.i686+PAE
Not setting the RLIMIT_DATA to zero in coregrind/m_main.c (valgrind_main) does
indeed work around it.
--
You are receiving this mai
https://bugs.kde.org/show_bug.cgi?id=357833
--- Comment #5 from Mark Wielaard ---
For reference here is the full commit explaining that previously the
RLIMIT_DATA value indeed was mostly harmless only affecting brk, but now
restricts any data area allocations:
commit 84638335900f1995495838fe1bd4
https://bugs.kde.org/show_bug.cgi?id=358213
--- Comment #2 from Mark Wielaard ---
The patch to the testscase only works for helgrind, but the test program is
also used under drd. It needs some different changes or you will get two
failures:
drd/tests/bar_bad(stderr)
drd/t
https://bugs.kde.org/show_bug.cgi?id=357833
--- Comment #6 from Mark Wielaard ---
Created attachment 96751
--> https://bugs.kde.org/attachment.cgi?id=96751&action=edit
Remove setting zero RLIMIT_DATA
The simplest seems to be to just remove the zero data rlimit. It also gets rid
of some nasty h
https://bugs.kde.org/show_bug.cgi?id=358030
Mark Wielaard changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=357833
Mark Wielaard changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=358213
Mark Wielaard changed:
What|Removed |Added
Summary|helgrind bar_bad testcase |helgrind/drd bar_bad
|hangs w
https://bugs.kde.org/show_bug.cgi?id=358213
Mark Wielaard changed:
What|Removed |Added
Attachment #96738|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=358213
--- Comment #5 from Mark Wielaard ---
Note that patch is missing the drd/test/Makefile.am addition of the two extra
exp file:
diff --git a/drd/tests/Makefile.am b/drd/tests/Makefile.am
index 2885391..cfd74d0 100644
--- a/drd/tests/Makefile.am
+++ b/drd
https://bugs.kde.org/show_bug.cgi?id=359201
Mark Wielaard changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=359201
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=359703
Bug ID: 359703
Summary: s390: wire up separate socketcalls system calls
Product: valgrind
Version: 3.11 SVN
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severit
https://bugs.kde.org/show_bug.cgi?id=359703
--- Comment #1 from Mark Wielaard ---
Created attachment 97376
--> https://bugs.kde.org/attachment.cgi?id=97376&action=edit
S390 Split Socketcall
Proposed patch. Simply wires up the split out system calls directly to the
existing syswrap handlers.
-
https://bugs.kde.org/show_bug.cgi?id=359703
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=359724
Bug ID: 359724
Summary: getsockname syscall might crash - deref_UInt should
check make sure it is safe to deref
Product: valgrind
Version: unspecified
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=359724
Mark Wielaard changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=359733
Bug ID: 359733
Summary: amd64 implement strchr/index override to avoid need
for suppression and redirection like x86
Product: valgrind
Version: unspecified
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=359733
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=345307
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=345307
--- Comment #10 from Mark Wielaard ---
The __gnu_cxx::__freeres patch looks really good. I have been testing it with
the gcc patch on x86_64-pc-linux-gnu. And things look fine. No more still
reachable leaks.
Only question is whether we really need both
https://bugs.kde.org/show_bug.cgi?id=345307
--- Comment #13 from Mark Wielaard ---
(In reply to Ivo Raisr from comment #11)
> Yes, it can be done with just one FREERES_DONE hook.
> But it means we need to pass argument(s) to it (which __freeres functions to
> call) and this will involve some extr
https://bugs.kde.org/show_bug.cgi?id=359503
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--- Comment #6 from Mark Wielaa
https://bugs.kde.org/show_bug.cgi?id=359503
Mark Wielaard changed:
What|Removed |Added
Attachment #97762|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=359503
--- Comment #8 from Mark Wielaard ---
Created attachment 97787
--> https://bugs.kde.org/attachment.cgi?id=97787&action=edit
Add arm64 scalar test. Enable tested syscalls.
This adds a new memcheck/tests/arm64-linux/scalar test which is based on the
me
https://bugs.kde.org/show_bug.cgi?id=359503
--- Comment #9 from Mark Wielaard ---
Created attachment 97794
--> https://bugs.kde.org/attachment.cgi?id=97794&action=edit
Add more missing syscalls
This adds most of the missing syscalls from the original patch for which I
could do a quick test on
https://bugs.kde.org/show_bug.cgi?id=359503
Mark Wielaard changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=345307
--- Comment #15 from Mark Wielaard ---
Created attachment 97829
--> https://bugs.kde.org/attachment.cgi?id=97829&action=edit
libstdc++.supp
This is the patch the valgrind fedora package is currently using as a
workaround till we get proper __gnu_cxx:
https://bugs.kde.org/show_bug.cgi?id=360425
Bug ID: 360425
Summary: arm64 unsupported instruction ldpsw
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=360519
Bug ID: 360519
Summary: none/tests/arm64/memory.vgtest might fail with newer
gcc
Product: valgrind
Version: 3.11 SVN
Platform: Other
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=360519
--- Comment #1 from Mark Wielaard ---
Created attachment 97892
--> https://bugs.kde.org/attachment.cgi?id=97892&action=edit
Place nops around ldr literal test instruction and adjust expected output
--
You are receiving this mail because:
You are wat
https://bugs.kde.org/show_bug.cgi?id=360425
--- Comment #1 from Mark Wielaard ---
Created attachment 97896
--> https://bugs.kde.org/attachment.cgi?id=97896&action=edit
VEX implementation of ldpsw
I couldn't find a precise arm64 instruction encoding table, so needed some
experimenting to see wh
https://bugs.kde.org/show_bug.cgi?id=360425
--- Comment #2 from Mark Wielaard ---
Created attachment 97897
--> https://bugs.kde.org/attachment.cgi?id=97897&action=edit
tests for ldpsw
This groups the ldpsw tests with the ldp tests. Which causes some extra changes
in later tests. Maybe the new
https://bugs.kde.org/show_bug.cgi?id=360425
--- Comment #4 from Mark Wielaard ---
(In reply to Peter Maydell from comment #3)
> (In reply to Mark Wielaard from comment #1)
> > I couldn't find a precise arm64 instruction encoding table
>
> This is all documented in the ARMv8 Architecture Referenc
https://bugs.kde.org/show_bug.cgi?id=360519
Mark Wielaard changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=360425
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=358478
Bug ID: 358478
Summary: drd/tests/std_thread.cpp doesn't build with GCC6
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Sev
https://bugs.kde.org/show_bug.cgi?id=358478
--- Comment #1 from Mark Wielaard ---
Some for drd/tests/std_thread2.cpp which uses the same "trick".
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=358478
--- Comment #4 from Mark Wielaard ---
(In reply to Bart Van Assche from comment #2)
> Are gcc 6 RPMs available somewhere ?
I am afraid not yet. I am using a hand build GCC6 for now.
But Fedora rawhide is supposed to do a mass-rebuild against gcc6 soon.
https://bugs.kde.org/show_bug.cgi?id=358478
Mark Wielaard changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=359201
Bug ID: 359201
Summary: futex syscall "skips" argument 5 if op is
FUTEXT_WAIT_BITSET
Product: valgrind
Version: 3.11 SVN
Platform: Other
URL: https://bugzilla.redha
https://bugs.kde.org/show_bug.cgi?id=359289
Bug ID: 359289
Summary: s390x: popcnt (B9E1) not implemented
Product: valgrind
Version: unspecified
Platform: Other
URL: https://bugzilla.redhat.com/show_bug.cgi?id=1306844
https://bugs.kde.org/show_bug.cgi?id=359289
--- Comment #2 from Mark Wielaard ---
Thanks. Works for me on both the original program (libgccjit) and the simple
reproducer.
BTW. I believe the patch is missing an update to none/tests/s390x/Makefile.am
to make sure the new test is build and the vgte
https://bugs.kde.org/show_bug.cgi?id=359201
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=360571
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=370265
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--- Comment #3 from Mark Wielaa
https://bugs.kde.org/show_bug.cgi?id=370265
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=358213
Mark Wielaard changed:
What|Removed |Added
Summary|helgrind/drd bar_bad|helgrind/drd bar_bad
|testcas
https://bugs.kde.org/show_bug.cgi?id=371396
Bug ID: 371396
Summary: helgrind and drd pth_cond_destroy_busy testcase hang
with new glibc cond var implementation
Product: valgrind
Version: 3.12 SVN
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=371396
--- Comment #1 from Mark Wielaard ---
A workaround (skip the test if a newer glibc is detected) has been checked in
as valgrind r16097.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359952
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--- Comment #1 from Mark Wielaa
https://bugs.kde.org/show_bug.cgi?id=369000
Bug ID: 369000
Summary: AMD64 fma4 instructions unsupported. vex amd64->IR:
unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1
0x4 0xC5 0xF9
Product: valgrind
Version
https://bugs.kde.org/show_bug.cgi?id=339596
Mark Wielaard changed:
What|Removed |Added
Blocks||369000
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=339596
Mark Wielaard changed:
What|Removed |Added
Summary|AMD64 fma4 and xop |AMD64 xop instructions
|instr
https://bugs.kde.org/show_bug.cgi?id=369000
--- Comment #1 from Mark Wielaard ---
Created attachment 101169
--> https://bugs.kde.org/attachment.cgi?id=101169&action=edit
Implement AMD FMA4 instructions.
This is just the FMA4 part of the patch proposed in bug #339596. The original
patch is by p
https://bugs.kde.org/show_bug.cgi?id=369000
--- Comment #2 from Mark Wielaard ---
Created attachment 101170
--> https://bugs.kde.org/attachment.cgi?id=101170&action=edit
Testcases for fma4 instructions.
This is an extension of the testcases for the fma4 instructions I wrote for bug
#339596.
T
https://bugs.kde.org/show_bug.cgi?id=369000
--- Comment #3 from Mark Wielaard ---
VEX svn r3249 and valgrind svn r15961
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=358213
--- Comment #6 from Mark Wielaard ---
I checked in a workaround for the hang based on the attachement as valgrind svn
r15962.
This does make sure that the tests don't hang indefenitely. But they do
introduce (more) non-determinism that occassionally ca
https://bugs.kde.org/show_bug.cgi?id=369000
Mark Wielaard changed:
What|Removed |Added
Depends on|339596 |
Blocks|
https://bugs.kde.org/show_bug.cgi?id=339596
Mark Wielaard changed:
What|Removed |Added
Blocks|369000 |
Depends on|
https://bugs.kde.org/show_bug.cgi?id=339596
Mark Wielaard changed:
What|Removed |Added
Depends on||369053
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=369053
Bug ID: 369053
Summary: AMD64 fma4 instructions missing 256 bit support
Product: valgrind
Version: 3.9.0
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity:
https://bugs.kde.org/show_bug.cgi?id=369000
Mark Wielaard changed:
What|Removed |Added
Blocks||369053
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=339596
Bug 339596 depends on bug 369000, which changed state.
Bug 369000 Summary: AMD64 fma4 instructions unsupported. vex amd64->IR:
unhandled instruction bytes: 0x8F 0xE8 0x78 0xCD 0xC1 0x4 0xC5 0xF9
https://bugs.kde.org/show_bug.cgi?id=369000
Wh
https://bugs.kde.org/show_bug.cgi?id=369169
Bug ID: 369169
Summary: ppc64 fails jm_int_isa_2_07 test
Product: valgrind
Version: 3.12 SVN
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=369169
--- Comment #1 from Mark Wielaard ---
Created attachment 101218
--> https://bugs.kde.org/attachment.cgi?id=101218&action=edit
test output
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=369169
--- Comment #2 from Mark Wielaard ---
Created attachment 101219
--> https://bugs.kde.org/attachment.cgi?id=101219&action=edit
diff with expected output
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=369169
--- Comment #3 from Mark Wielaard ---
Created attachment 101220
--> https://bugs.kde.org/attachment.cgi?id=101220&action=edit
diff with LE expected output
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=369169
--- Comment #4 from Mark Wielaard ---
The diffs are the same because the none/tests/ppc64/jm_int_isa_2_07.stdout.exp
and none/tests/ppc64/jm_int_isa_2_07.stdout.exp-LE expect files are the same.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=369175
Bug ID: 369175
Summary: jm_vec_isa_2_07 test crashes on ppc64
Product: valgrind
Version: 3.12 SVN
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=369175
--- Comment #1 from Mark Wielaard ---
Note that running the program itself (not under valgrind) seems fine.
It is only when ran under valgrind that it produces the SIGSEGV:
==28394== Process terminating with default action of signal 11 (SIGSEGV)
==2839
https://bugs.kde.org/show_bug.cgi?id=369169
--- Comment #6 from Mark Wielaard ---
(In reply to Carl Love from comment #5)
> Please test the patch and see if the regression test results are as expected
> on your machine.
They PASS. Thanks.
--
You are receiving this mail because:
You are watchin
https://bugs.kde.org/show_bug.cgi?id=368120
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--- Comment #1 from Mark Wielaa
https://bugs.kde.org/show_bug.cgi?id=357932
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--- Comment #3 from Mark Wielaa
https://bugs.kde.org/show_bug.cgi?id=357932
--- Comment #4 from Mark Wielaard ---
Or maybe Julian means the "redundant" REXB is altering the e register field and
so it needs further adjustment to get the correct register if REXB is set.
Anyway, a testcase and how to (or what) generates it would
https://bugs.kde.org/show_bug.cgi?id=368419
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--- Comment #4 from Mark Wielaa
https://bugs.kde.org/show_bug.cgi?id=369209
Bug ID: 369209
Summary: valgrind loops and eats up all memory (very slowly)
when the current working directory doesn't exist.
Product: valgrind
Version: 3.12 SVN
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=369209
--- Comment #1 from Mark Wielaard ---
Created attachment 101237
--> https://bugs.kde.org/attachment.cgi?id=101237&action=edit
Don't require the current working directory to exist.
At startup valgrind fetches the current working directory and stashes
https://bugs.kde.org/show_bug.cgi?id=369209
Mark Wielaard changed:
What|Removed |Added
CC||iv...@ivosh.net,
|
https://bugs.kde.org/show_bug.cgi?id=369175
--- Comment #6 from Mark Wielaard ---
(In reply to Julian Seward from comment #3)
> I tried to reproduce this on gcc112.fsffrance.org (a P8 system) but failed --
> it runs OK. I'd be happy to chase this if I could reproduce on a machine
> that I can ac
https://bugs.kde.org/show_bug.cgi?id=369175
--- Comment #9 from Mark Wielaard ---
Assuming that is with remote vgdb attached then you should be able to get the
generated IR and assembly with:
monitor v.translate 0x100016dc 0b0011
(See the manual or valgrind --help-debug for the expl
https://bugs.kde.org/show_bug.cgi?id=369175
--- Comment #18 from Mark Wielaard ---
Never mind the objdump -h gives the right information. The 0x3824B2B0 is indeed
in the middle of the ODP. The ODP is loaded and DATA (not CODE), which I assume
means it is readable (so we can load/read the actual f
https://bugs.kde.org/show_bug.cgi?id=369175
--- Comment #17 from Mark Wielaard ---
Since some of the output looks as if we jump into (or just read from?) the ODP
and that gives a permission error/SEGV, could you provide the section and
segments of the tool to double check everything is at the rig
https://bugs.kde.org/show_bug.cgi?id=369209
--- Comment #5 from Mark Wielaard ---
(In reply to Ivo Raisr from comment #4)
> So this simple change fixes the warning:
> - execlp ("echo", "echo", "Hello", "World", NULL);
> + execlp ("echo", "echo", "Hello", "World", (char *) NULL);
Thanks, fixed
https://bugs.kde.org/show_bug.cgi?id=369264
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--- Comment #1 from Mark Wielaa
https://bugs.kde.org/show_bug.cgi?id=369356
Bug ID: 369356
Summary: pre_mem_read_sockaddr syscall wrapper can crash with
bad sockaddr
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=369356
--- Comment #1 from Mark Wielaard ---
Created attachment 101286
--> https://bugs.kde.org/attachment.cgi?id=101286&action=edit
Fix pre_mem_read_sockaddr crash on invalid syscall arguments
Don't do any more checks if it isn't safe to inspect the addres
https://bugs.kde.org/show_bug.cgi?id=369359
Bug ID: 369359
Summary: msghdr_foreachfield can crash when handling bad iovec
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=369359
--- Comment #1 from Mark Wielaard ---
Created attachment 101287
--> https://bugs.kde.org/attachment.cgi?id=101287&action=edit
Fix crash in msghdr_foreachfield when iov_len isn't safe to dereference.
Also stop checking when max length of bytes have be
https://bugs.kde.org/show_bug.cgi?id=369360
Bug ID: 369360
Summary: Bad sigprocmask old or new sets can crash valgrind
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
S
https://bugs.kde.org/show_bug.cgi?id=369360
--- Comment #1 from Mark Wielaard ---
Created attachment 101288
--> https://bugs.kde.org/attachment.cgi?id=101288&action=edit
Fix crash when old/new sigprocmask isn't safe to dereference
Since we want to use the set and oldset for bookkeeping we also
https://bugs.kde.org/show_bug.cgi?id=369361
Bug ID: 369361
Summary: vmsplice syscall wrapper crashes on bad iovec
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severi
1 - 100 of 336 matches
Mail list logo
