https://bugs.kde.org/show_bug.cgi?id=475650
Bart Van Assche changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=475650
Bart Van Assche changed:
What|Removed |Added
CC||bart.vanassche+...@gmail.co
https://bugs.kde.org/show_bug.cgi?id=445743
Bart Van Assche changed:
What|Removed |Added
Assignee|bart.vanassche+...@gmail.co |jsew...@acm.org
|m
https://bugs.kde.org/show_bug.cgi?id=444568
Bart Van Assche changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=445743
Bart Van Assche changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=435160
--- Comment #11 from Bart Van Assche ---
"Patch v2" has been applied on the master branch. Thanks for the patch!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435160
--- Comment #8 from Bart Van Assche ---
Please provide a .stderr.exp file that makes the test pass on your test setup.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435160
--- Comment #5 from Bart Van Assche ---
Reverting commit 719d23b7a9c3 ("drd/tests/swapcontext: Improve portability") is
not an option. Valgrind source code must build and run on all supported
operating systems. Not all supported operati
https://bugs.kde.org/show_bug.cgi?id=434775
--- Comment #4 from Bart Van Assche ---
Please retest with commit 7cd4d78163fa ("memcheck/tests/linux/stack_changes:
Only run this test if setcontext() is available").
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=434775
--- Comment #2 from Bart Van Assche ---
I took a look at the attached patch and noticed multiple new #ifdefs. I'm
concerned that adding so many #ifdefs would make the test harder to maintain.
So I added a configure test for swapcontext(). Can you take
https://bugs.kde.org/show_bug.cgi?id=432381
Bart Van Assche changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=432381
--- Comment #3 from Bart Van Assche ---
I should have noticed the attachment myself.
Do you want to root-cause this bug and propose a patch or do you perhaps expect
me to look into this? A good start would be to verify whether
https://bugs.kde.org/show_bug.cgi?id=432381
--- Comment #1 from Bart Van Assche ---
Sharing the source code of a reproducer would help a lot ...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=428909
--- Comment #23 from Bart Van Assche ---
On 12/3/20 6:54 AM, Paul Floyd wrote:
> https://bugs.kde.org/show_bug.cgi?id=428909
>
> --- Comment #22 from Paul Floyd ---
> (In reply to Mark Wielaard from comment #20)
>>
>> Normally
https://bugs.kde.org/show_bug.cgi?id=382083
Bart Van Assche changed:
What|Removed |Added
CC||bvanass...@acm.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=428909
Bart Van Assche changed:
What|Removed |Added
CC||bvanass...@acm.org
--- Comment #16 from Bart
https://bugs.kde.org/show_bug.cgi?id=428035
Bart Van Assche changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=428035
Bart Van Assche changed:
What|Removed |Added
CC||bvanass...@acm.org
--- Comment #1 from Bart
https://bugs.kde.org/show_bug.cgi?id=426144
Bart Van Assche changed:
What|Removed |Added
Summary|DRD reportes "condition |DRD reports "
https://bugs.kde.org/show_bug.cgi?id=403212
Bart Van Assche changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=426144
Bart Van Assche changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=426144
--- Comment #2 from Bart Van Assche ---
Maybe a new version of pthread_cond_init has been added in the Fedora 33 glibc
library. I will take a look.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416286
Bart Van Assche changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=403212
Bart Van Assche changed:
What|Removed |Added
CC||bvanass...@acm.org
--- Comment #3 from Bart
https://bugs.kde.org/show_bug.cgi?id=416286
--- Comment #2 from Bart Van Assche ---
Thanks for having reported this. Please check whether the changes that have
been checked in on the master branch fix this issue.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410757
--- Comment #5 from Bart Van Assche ---
Please have a look at commit 0f7483d1d8a8
("memcheck/tests/sys-preadv2_pwritev2: Check whether these syscalls are
supported").
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410757
Bart Van Assche changed:
What|Removed |Added
CC||bvanass...@acm.org
--- Comment #3 from Bart
https://bugs.kde.org/show_bug.cgi?id=407764
--- Comment #2 from Bart Van Assche ---
Have you considered to change ", cond" into ", " in the printf()
statement?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405716
Bart Van Assche changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=403212
--- Comment #1 from Bart Van Assche ---
This proposal sounds good to me.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402341
--- Comment #1 from Bart Van Assche ---
Thank you for your report. Please verify whether commit 5b4029b8cc8f
("drd/tests/tsan_thread_wrappers_pthread.h: Fix MyThread::ThreadBody()") fixes
this bug.
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=402341
Bart Van Assche changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=401578
Bart Van Assche changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=393351
--- Comment #1 from Bart Van Assche ---
This is reproducible with the latest Valgrind version (git commit ID
0375954c18d918045d4d7bfb30061f445511c3d3).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356374
Bart Van Assche <bvanass...@acm.org> changed:
What|Removed |Added
Status|UNCONFIRMED |RE
https://bugs.kde.org/show_bug.cgi?id=357010
Bart Van Assche <bvanass...@acm.org> changed:
What|Removed |Added
Resolution|--- |W
https://bugs.kde.org/show_bug.cgi?id=393351
Bart Van Assche <bvanass...@acm.org> changed:
What|Removed |Added
Ever confirmed|0 |1
https://bugs.kde.org/show_bug.cgi?id=393351
Bug ID: 393351
Summary: unhandled instruction bytes: 0x62 0xF1 0xFD 0x48 0x6F
0xD 0xE1 0xEC 0x8 0x0
Product: valgrind
Version: unspecified
Platform: Other
OS:
https://bugs.kde.org/show_bug.cgi?id=381115
--- Comment #10 from Bart Van Assche <bvanass...@acm.org> ---
Thanks Wolfgang for the feedback. By running the following command I got rid of
the freezing behavior:
rpm -e plasma5-workspace sddm-theme-openSUSE-42.1.1-20.1.noarch
plasma5-wor
https://bugs.kde.org/show_bug.cgi?id=380974
Bart Van Assche <bvanass...@acm.org> changed:
What|Removed |Added
CC||bvanass...@a
https://bugs.kde.org/show_bug.cgi?id=380923
Bart Van Assche <bvanass...@acm.org> changed:
What|Removed |Added
CC||bvanass...@a
https://bugs.kde.org/show_bug.cgi?id=381115
Bart Van Assche <bvanass...@acm.org> changed:
What|Removed |Added
Ever confirmed|0 |1
https://bugs.kde.org/show_bug.cgi?id=356374
--- Comment #4 from Bart Van Assche <bvanass...@acm.org> ---
Sorry for the delay. r16342 should fix this bug.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=374414
--- Comment #4 from Bart Van Assche <bvanass...@acm.org> ---
I do not agree that a loop like "while (!ready) cv.wait(lk);" would be a
correct way to wait for cv to be signaled. If a sleep() statement would be
inserted before or inside th
https://bugs.kde.org/show_bug.cgi?id=374414
Bart Van Assche <bvanass...@acm.org> changed:
What|Removed |Added
CC||bvanass...@a
https://bugs.kde.org/show_bug.cgi?id=373166
--- Comment #9 from Bart Van Assche <bvanass...@acm.org> ---
Analyzing software with Helgrind and DRD may trigger other code paths compared
to analyzing the same software with memcheck. My proposal is to start with
looking into why VEX r
https://bugs.kde.org/show_bug.cgi?id=373166
--- Comment #7 from Bart Van Assche <bvanass...@acm.org> ---
Everyone RHEL user I know either uses RHEL 6 or RHEL 7. How relevant is RHEL 4
today?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373166
--- Comment #3 from Bart Van Assche <bvanass...@acm.org> ---
Hi Tushar, are you aware that the "unhandled instruction bytes" message
indicates a bug in VEX and not in DRD nor in Helgrind? See also
http://valgrind.org/docs/manual/faq.h
https://bugs.kde.org/show_bug.cgi?id=352395
Bart Van Assche <bvanass...@acm.org> changed:
What|Removed |Added
CC||bvanass...@a
https://bugs.kde.org/show_bug.cgi?id=363740
Bart Van Assche <bvanass...@acm.org> changed:
What|Removed |Added
Assignee|jsew...@acm.org |bugzilla@po
https://bugs.kde.org/show_bug.cgi?id=363740
Bart Van Assche <bvanass...@acm.org> changed:
What|Removed |Added
CC||bvanass...@a
https://bugs.kde.org/show_bug.cgi?id=358478
Bart Van Assche <bvanass...@acm.org> changed:
What|Removed |Added
Ever confirmed|0 |1
https://bugs.kde.org/show_bug.cgi?id=358478
--- Comment #2 from Bart Van Assche <bvanass...@acm.org> ---
Are gcc 6 RPMs available somewhere ?
--
You are receiving this mail because:
You are watching all bug changes.
53 matches
Mail list logo