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=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=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=370265
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
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=369209
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=369356
Mark Wielaard changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=369356
--- Comment #2 from Mark Wielaard ---
valgrind svn r15990
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=369359
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=369360
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=369361
Mark Wielaard changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=369362
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=369383
Mark Wielaard changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=369402
Mark Wielaard changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=369441
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=369446
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=369209
--- Comment #9 from Mark Wielaard ---
(In reply to Ivo Raisr from comment #8)
> the new test case works ok (I am able to simulate the problem on Solaris)
> with 'make one component inaccessible'.
Thanks for testing. Lets go with this then.
> Please in
https://bugs.kde.org/show_bug.cgi?id=369175
--- Comment #30 from Mark Wielaard ---
(In reply to Carl Love from comment #29)
> Please review the patch and let me know if you see any issues. If everyone
> approves the patch and the ISA 3.0 Big endian test passes, I will commit the
> fix. The fix
https://bugs.kde.org/show_bug.cgi?id=369446
--- Comment #1 from Mark Wielaard ---
Created attachment 101322
--> https://bugs.kde.org/attachment.cgi?id=101322&action=edit
Don't crash, but warn and return EINVAL on unknown fcntl command.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=369446
Bug ID: 369446
Summary: valgrind crashes on unknown fcntl command
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity:
https://bugs.kde.org/show_bug.cgi?id=369441
Bug ID: 369441
Summary: bad lvec argument crashes process_vm_readv/writev
syscall wrappers
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=369441
--- Comment #1 from Mark Wielaard ---
Created attachment 101321
--> https://bugs.kde.org/attachment.cgi?id=101321&action=edit
Don't check bad iovec array in process_vm_readv/writev.
The TODO comment already said what to do.
--
You are receiving thi
https://bugs.kde.org/show_bug.cgi?id=369409
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--- Comment #1 from Mark Wielaa
https://bugs.kde.org/show_bug.cgi?id=369209
--- Comment #7 from Mark Wielaard ---
Created attachment 101309
--> https://bugs.kde.org/attachment.cgi?id=101309&action=edit
new nocwd testcase
How about this variant of the test.
It tries a couple of things to make sure getcwd will fail.
Create a p
https://bugs.kde.org/show_bug.cgi?id=369402
--- Comment #1 from Mark Wielaard ---
Created attachment 101307
--> https://bugs.kde.org/attachment.cgi?id=101307&action=edit
linux-x86 check get/set_thread_area pointer before use.
--
You are receiving this mail because:
You are watching all bug ch
https://bugs.kde.org/show_bug.cgi?id=369402
Bug ID: 369402
Summary: Bad set/get_thread_area pointer crashes valgrind
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Sev
https://bugs.kde.org/show_bug.cgi?id=369383
--- Comment #1 from Mark Wielaard ---
Created attachment 101298
--> https://bugs.kde.org/attachment.cgi?id=101298&action=edit
Fix crash in sys_modify_ldt wrapper on bad ptr.
Make sure ptr is safe_to_deref if not NULL.
Also fixup some corner case erro
https://bugs.kde.org/show_bug.cgi?id=369383
Bug ID: 369383
Summary: x86 sys_modify_ldt wrapper crashes on bad ptr
Product: valgrind
Version: 3.12 SVN
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity:
https://bugs.kde.org/show_bug.cgi?id=369175
--- Comment #21 from Mark Wielaard ---
Created attachment 101296
--> https://bugs.kde.org/attachment.cgi?id=101296&action=edit
Patch to wrap &is_BCDstring128_helper address in fnptr_to_fnentry
After some debugging Julian suggested this fix. It makes
https://bugs.kde.org/show_bug.cgi?id=369175
--- Comment #20 from Mark Wielaard ---
Created attachment 101295
--> https://bugs.kde.org/attachment.cgi?id=101295&action=edit
Trace for smaller badness2 reproducer
Trace output for a smaller reproducer:
$ cat badness2.c
#include
static vector un
https://bugs.kde.org/show_bug.cgi?id=369362
--- Comment #1 from Mark Wielaard ---
Created attachment 101290
--> https://bugs.kde.org/attachment.cgi?id=101290&action=edit
Fix crash in linux [rt_]sigaction wrapper with bad old/new sigaction handler.
Since we try to modify the old/new sigaction h
https://bugs.kde.org/show_bug.cgi?id=369362
Bug ID: 369362
Summary: Bad sigaction arguments crash valgrind
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: nor
https://bugs.kde.org/show_bug.cgi?id=369361
--- Comment #1 from Mark Wielaard ---
Created attachment 101289
--> https://bugs.kde.org/attachment.cgi?id=101289&action=edit
Fix crash in vmsplice linux kernel wrapper when iovec is bad
--
You are receiving this mail because:
You are watching all b
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
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=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=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=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=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=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=369264
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--- Comment #1 from Mark Wielaa
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=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=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 #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 #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=369209
Mark Wielaard changed:
What|Removed |Added
CC||iv...@ivosh.net,
|
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
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=368419
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--- Comment #4 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=357932
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--- Comment #3 from Mark Wielaa
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=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=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=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=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=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 #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 #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
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=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=369000
Mark Wielaard changed:
What|Removed |Added
Blocks||369053
--
You are receiving this mail because:
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=339596
Mark Wielaard changed:
What|Removed |Added
Blocks|369000 |
Depends on|
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=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
--- 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=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 #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=339596
Mark Wielaard changed:
What|Removed |Added
Summary|AMD64 fma4 and xop |AMD64 xop instructions
|instr
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=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=355188
Mark Wielaard changed:
What|Removed |Added
CC||y...@tsoft.com
--- Comment #6 from Mark Wielaar
https://bugs.kde.org/show_bug.cgi?id=368861
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=322935
--- Comment #34 from Mark Wielaard ---
(In reply to Peter Maydell from comment #33)
> (In reply to Mark Wielaard from comment #32)
> > valgrind should already intercept the memcmp from glibc. This one however is
> > in a different library libcofi_rpi.so
https://bugs.kde.org/show_bug.cgi?id=322935
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--- Comment #32 from Mark Wiela
https://bugs.kde.org/show_bug.cgi?id=364948
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--- Comment #11 from Mark Wiela
https://bugs.kde.org/show_bug.cgi?id=359503
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=368791
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--- Comment #2 from Mark Wielaa
https://bugs.kde.org/show_bug.cgi?id=368791
Mark Wielaard changed:
What|Removed |Added
Summary|unhandled syscall: 167 |unhandled amd64-linux
|
https://bugs.kde.org/show_bug.cgi?id=368461
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--- Comment #4 from Mark Wielaa
https://bugs.kde.org/show_bug.cgi?id=361726
--- Comment #6 from Mark Wielaard ---
BTW. This is an awesome overview of all the linux syscalls by architectures:
https://fedora.juszkiewicz.com.pl/syscalls.html
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=361726
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=358620
Mark Wielaard changed:
What|Removed |Added
Summary|ARM: unhandled syscall: 357 |ARM: disInstr(arm):
|
https://bugs.kde.org/show_bug.cgi?id=368412
--- Comment #6 from Mark Wielaard ---
Thanks, pushed as valgrind svn r15952
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359181
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=368412
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--- Comment #3 from Mark Wielaa
https://bugs.kde.org/show_bug.cgi?id=359181
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|jsew...@acm.org
https://bugs.kde.org/show_bug.cgi?id=339596
Mark Wielaard changed:
What|Removed |Added
Summary|vex amd64->IR: unhandled|AMD64 fma4 and xop
|instructi
https://bugs.kde.org/show_bug.cgi?id=339596
--- Comment #19 from Mark Wielaard ---
Created attachment 100956
--> https://bugs.kde.org/attachment.cgi?id=100956&action=edit
Current stdout.diff file for new fma4.vgtest and proposed patch
--
You are receiving this mail because:
You are watching a
https://bugs.kde.org/show_bug.cgi?id=339596
--- Comment #18 from Mark Wielaard ---
Created attachment 100955
--> https://bugs.kde.org/attachment.cgi?id=100955&action=edit
Testcases for fma4 instructions
Here are some testcases for the FMA4 instructions. I haven't looked yet at the
XOP instruct
https://bugs.kde.org/show_bug.cgi?id=339596
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--- Comment #17 from Mark Wiela
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=359952
Mark Wielaard changed:
What|Removed |Added
CC||m...@redhat.com
--- Comment #1 from Mark Wielaa
https://bugs.kde.org/show_bug.cgi?id=364413
--- Comment #3 from Mark Wielaard ---
I made a typo which caused:
...checking makefile consistency
none/tests/Makefile.am:1: error: pselect_sigmask_null.vgtest is missing in
EXTRA_DIST
none/tests/Makefile.am:1: error: pselect_signask_null.vgtest is in
https://bugs.kde.org/show_bug.cgi?id=364413
Mark Wielaard changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=364413
--- Comment #1 from Mark Wielaard ---
Created attachment 99546
--> https://bugs.kde.org/attachment.cgi?id=99546&action=edit
Proposed testcase and fix
When the last argument ss == NULL don't check whether it is valid and don't try
to copy the sigmask
https://bugs.kde.org/show_bug.cgi?id=364413
Bug ID: 364413
Summary: pselect sycallwrapper mishandles NULL sigmask
Product: valgrind
Version: 3.11 SVN
Platform: Other
URL: https://bugzilla.redhat.com/show_bug.cgi?id=1344082
1 - 100 of 168 matches
Mail list logo
