[valgrind] [Bug 475650] DRD does not work with C11 threads
https://bugs.kde.org/show_bug.cgi?id=475650
Bart Van Assche changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Bart Van Assche ---
The following two additional commits have been pushed:
* 45590cee742b ("drd/tests/thrd_create: Convert from C++ to C")
* a9d065c48d35 ("configure.ac: Convert the thrd_create() test from C++ to C")
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 475650] DRD does not work with C11 threads
https://bugs.kde.org/show_bug.cgi?id=475650 Bart Van Assche changed: What|Removed |Added CC||bart.vanassche+...@gmail.co ||m --- Comment #2 from Bart Van Assche --- Does commit 6cea271f436d help? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 445743] "The impossible happened: mutex is locked simultaneously by two threads" while using mutexes with priority inheritance and signals
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 | -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 444568] drd/tests/pth_barrier_thr_cr Number of concurrent pthread_barrier_wait() calls exceeds the barrier count
https://bugs.kde.org/show_bug.cgi?id=444568
Bart Van Assche changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Bart Van Assche ---
Commit 72b556ab15f1 ("drd: Improve barrier support") should fix this bug.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 445743] "The impossible happened: mutex is locked simultaneously by two threads" while using mutexes with priority inheritance and signals
https://bugs.kde.org/show_bug.cgi?id=445743
Bart Van Assche changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0 |1
--- Comment #7 from Bart Van Assche ---
Please take a look at commit bf0579a44a44 ("drd: Add a test program that
interrupts pthread_mutex_lock()"). If I run the new test program (the program
attached to this bug with minor changes) natively then the text "unlock"
appears before the text "contender locked mutex". If I run that program under
memcheck then the order of these two output lines is reversed. So I think this
indicates a bug in the Valgrind core.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 435160] drd/tests/swapcontext.c: threads are interrupted in nanosleep
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.
[valgrind] [Bug 435160] drd/tests/swapcontext.c: threads are interrupted in nanosleep
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.
[valgrind] [Bug 435160] drd/tests/swapcontext.c: threads are interrupted in nanosleep
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 operating systems support poll().
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 434775] drd/tests/swapcontext.c doesn't build with musl
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.
[valgrind] [Bug 434775] drd/tests/swapcontext.c doesn't build with musl
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 a look at commit
c9e88f3459e2 ("configure, drd: Only build the swapcontext test if swapcontext()
is available") and verify whether that is sufficient to make Valgrind build
again against musl?
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 432381] drd: drd_main.c:378 (drd_stop_using_mem): Assertion 'a1 <= a2' failed
https://bugs.kde.org/show_bug.cgi?id=432381 Bart Van Assche changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Bart Van Assche --- A candidate fix has been checked in on the master branch. Please retest. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 432381] drd: drd_main.c:378 (drd_stop_using_mem): Assertion 'a1 <= a2' failed
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 drd_start_using_mem_stack() gets called if VALGRIND_STACK_REGISTER() is used. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 432381] drd: drd_main.c:378 (drd_stop_using_mem): Assertion 'a1 <= a2' failed
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.
[valgrind] [Bug 428909] helgrind: need to intercept duplicate libc definitions for Fedora 33
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 I would agree with Bart, but I think this is one example of when >> configure tests are actually harder to keep correct than the simple ifdefs >> based on platform. > > I'll wait to see what Bart says before proceeding. If Mark agrees to maintain the #ifdef's, I'm fine with the ifdefs. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 382083] Failure to detect MUSL consistently.
https://bugs.kde.org/show_bug.cgi?id=382083 Bart Van Assche changed: What|Removed |Added CC||bvanass...@acm.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 428909] helgrind: need to intercept duplicate libc definitions for Fedora 33
https://bugs.kde.org/show_bug.cgi?id=428909 Bart Van Assche changed: What|Removed |Added CC||bvanass...@acm.org --- Comment #16 from Bart Van Assche --- ifdef-code like the following is hard to maintain: +#if defined(VGO_darwin) +#define VG_WRAP_THREAD_FUNCTION_LIBPTHREAD_ONLY +#elif defined(VGO_solaris) || (defined(VGO_linux) && defined(MUSL_LIBC)) +#define VG_WRAP_THREAD_FUNCTION_LIBC_ONLY +#elif defined(VGO_linux) +#define VG_WRAP_THREAD_FUNCTION_LIBC_AND_LIBPTHREAD +#else +# error "Unknown platform" +#endif Please change this into configure tests that verify whether pthreads functions exist in libpthread, libc or in both. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 428035] drd: dont need to intercept duplicate libc definitions if run with musl
https://bugs.kde.org/show_bug.cgi?id=428035 Bart Van Assche changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Bart Van Assche --- Thanks for confirming! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 428035] drd: dont need to intercept duplicate libc definitions if run with musl
https://bugs.kde.org/show_bug.cgi?id=428035
Bart Van Assche changed:
What|Removed |Added
CC||bvanass...@acm.org
--- Comment #1 from Bart Van Assche ---
Does the following patch help?
diff --git a/drd/drd_pthread_intercepts.c b/drd/drd_pthread_intercepts.c
index 62c466f508ad..585aafe22e41 100644
--- a/drd/drd_pthread_intercepts.c
+++ b/drd/drd_pthread_intercepts.c
@@ -174,6 +174,13 @@ static int never_true;
ret_ty VG_WRAP_FUNCTION_ZZ(VG_Z_LIBC_SONAME,zf) argl_decl\
{ return implf argl; }
#else
+#ifdef MUSL_LIBC
+/* musl provides a single library that includes pthreads functions. */
+#define PTH_FUNC(ret_ty, zf, implf, argl_decl, argl)\
+ ret_ty VG_WRAP_FUNCTION_ZZ(VG_Z_LIBPTHREAD_SONAME,zf) argl_decl; \
+ ret_ty VG_WRAP_FUNCTION_ZZ(VG_Z_LIBPTHREAD_SONAME,zf) argl_decl \
+ { return implf argl; }
+#else
/*
* On Linux, intercept both the libc and the libpthread functions. At
* least glibc 2.32.9000 (Fedora 34) has an implementation of all pthread
@@ -188,6 +195,7 @@ static int never_true;
ret_ty VG_WRAP_FUNCTION_ZZ(VG_Z_LIBPTHREAD_SONAME,zf) argl_decl \
{ return implf argl; }
#endif
+#endif
/**
* Macro for generating three Valgrind interception functions: one with the
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 426144] DRD reports "condition variable has not been initialized" when spawning pthread threads
https://bugs.kde.org/show_bug.cgi?id=426144 Bart Van Assche changed: What|Removed |Added Summary|DRD reportes "condition |DRD reports "condition |variable has not been |variable has not been |initialized" when spawning |initialized" when spawning |pthread threads |pthread threads -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 403212] trylock test hangs on FreeBSD
https://bugs.kde.org/show_bug.cgi?id=403212 Bart Van Assche changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 426144] DRD reportes "condition variable has not been initialized" when spawning pthread threads
https://bugs.kde.org/show_bug.cgi?id=426144
Bart Van Assche changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Bart Van Assche ---
Does commit 15330adf7c24 ("drd: Port to Fedora 33") fix this bug?
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 426144] DRD reportes "condition variable has not been initialized" when spawning pthread threads
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.
[valgrind] [Bug 416286] DRD reports “conflicting load” error on std::mutex::lock
https://bugs.kde.org/show_bug.cgi?id=416286 Bart Van Assche changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 403212] trylock test hangs on FreeBSD
https://bugs.kde.org/show_bug.cgi?id=403212
Bart Van Assche changed:
What|Removed |Added
CC||bvanass...@acm.org
--- Comment #3 from Bart Van Assche ---
A candidate fix has been checked in as commit 20dc7278512c ("drd/tests/trylock,
FreeBSD: Fix a hang"). I'm not familiar enough with FreeBSD to review the
changes in FreeBSD-specific code.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 416286] DRD reports “conflicting load” error on std::mutex::lock
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.
[valgrind] [Bug 410757] glibc wrapper discrepancy for preadv2/pwritev2 system calls across different versions
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.
[valgrind] [Bug 410757] glibc wrapper discrepancy for preadv2/pwritev2 system calls across different versions
https://bugs.kde.org/show_bug.cgi?id=410757 Bart Van Assche changed: What|Removed |Added CC||bvanass...@acm.org --- Comment #3 from Bart Van Assche --- How about adding a runtime prereq test? From drd/tests/annotate_ignore_rw.vgtest: prereq: ./supported_libpthread >From memcheck/tests/amd64/sh-mem-vec256-plo-yes.vgtest: prereq: ../../../tests/x86_amd64_features amd64-avx -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 407764] drd cond_post_wait gets wrong (?) condition on s390x z13 system
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.
[valgrind] [Bug 405716] int-overflow in stack size Margin calculation
https://bugs.kde.org/show_bug.cgi?id=405716 Bart Van Assche changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Bart Van Assche --- A fix has been checked in on the master branch. Please verify. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 403212] trylock test hangs on FreeBSD
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.
[valgrind] [Bug 402341] drd/tests/tsan_thread_wrappers_pthread.h:369: suspicious code ?
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 because:
You are watching all bug changes.
[valgrind] [Bug 402341] drd/tests/tsan_thread_wrappers_pthread.h:369: suspicious code ?
https://bugs.kde.org/show_bug.cgi?id=402341 Bart Van Assche changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 401578] drd crashes on fork if previous thread finished
https://bugs.kde.org/show_bug.cgi?id=401578 Bart Van Assche changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Bart Van Assche --- Thank you for having reported this. A candidate fix has been checked in on the master branch. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 393351] unhandled instruction bytes: 0x62 0xF1 0xFD 0x48 0x6F 0xD 0xE1 0xEC 0x8 0x0
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.
[valgrind] [Bug 356374] Assertion 'DRD_(g_threadinfo)[tid].pt_threadid != INVALID_POSIX_THREADID' failed
https://bugs.kde.org/show_bug.cgi?id=356374 Bart Van Assche <bvanass...@acm.org> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 357010] drd regression tests fail to compile with Intel compiler
https://bugs.kde.org/show_bug.cgi?id=357010 Bart Van Assche <bvanass...@acm.org> changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #3 from Bart Van Assche <bvanass...@acm.org> --- Please reopen this bug if this behavior is reproducible with the latest version of the Intel compiler. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 393351] unhandled instruction bytes: 0x62 0xF1 0xFD 0x48 0x6F 0xD 0xE1 0xEC 0x8 0x0
https://bugs.kde.org/show_bug.cgi?id=393351 Bart Van Assche <bvanass...@acm.org> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 393351] New: unhandled instruction bytes: 0x62 0xF1 0xFD 0x48 0x6F 0xD 0xE1 0xEC 0x8 0x0
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: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: bvanass...@acm.org Target Milestone: --- With the latest git version of fio, the latest git version of Valgrind and gcc version 7.3.1 I encountered the following: $ ~bart/software/valgrind/vg-in-place ~bart/software/fio/fio --name=sata --filename=/dev/sdc --ioengine=libaio --ioscheduler=none --rw=randread --offset=200G --size=200G --direct=1 --thread=1 --iodepth=64 --norandommap=1 ==25027== Memcheck, a memory error detector ==25027== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==25027== Using Valgrind-3.14.0.GIT and LibVEX; rerun with -h for copyright info [ ... ] vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x48 0x6F 0xD 0xE1 0xEC 0x8 0x0 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=NONE vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 ==25027== valgrind: Unrecognised instruction at address 0x40f695. ==25027==at 0x40F695: fio_client_hash_init (client.c:94) ==25027==by 0x48D48C: __libc_csu_init (elf-init.c:88) ==25027==by 0x5E5DA17: (below main) (in /lib64/libc-2.27.so) ==25027== Your program just tried to execute an instruction that Valgrind ==25027== did not recognise. There are two possible reasons for this. ==25027== 1. Your program has a bug and erroneously jumped to a non-code ==25027==location. If you are running Memcheck and you just saw a ==25027==warning about a bad jump, it's probably your program's fault. ==25027== 2. The instruction is legitimate but Valgrind doesn't handle it, ==25027==i.e. it's Valgrind's fault. If you think this is the case or ==25027==you are not sure, please let us know and we'll try to fix it. ==25027== Either way, Valgrind will now raise a SIGILL signal which will ==25027== probably kill your program. ==25027== ==25027== Process terminating with default action of signal 4 (SIGILL): dumping core ==25027== Illegal opcode at address 0x40F695 ==25027==at 0x40F695: fio_client_hash_init (client.c:94) ==25027==by 0x48D48C: __libc_csu_init (elf-init.c:88) ==25027==by 0x5E5DA17: (below main) (in /lib64/libc-2.27.so) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 381115] tab completion in konsole freezes system for about 20s
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-workspace-branding-openSUSE-42.1.1-20.1.noarch sddm-branding-openSUSE-0.14.0-7.2.x86_64 sddm -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 380974] KMessageBox takes a few seconds to appear after clicking Apply in KDE Partition Manager
https://bugs.kde.org/show_bug.cgi?id=380974 Bart Van Assche <bvanass...@acm.org> changed: What|Removed |Added CC||bvanass...@acm.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 380923] Konsole hangs for a minute if it cannot activate a dbus notification service
https://bugs.kde.org/show_bug.cgi?id=380923 Bart Van Assche <bvanass...@acm.org> changed: What|Removed |Added CC||bvanass...@acm.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 381115] tab completion in konsole freezes system for about 20s
https://bugs.kde.org/show_bug.cgi?id=381115 Bart Van Assche <bvanass...@acm.org> changed: What|Removed |Added Ever confirmed|0 |1 CC||bvanass...@acm.org Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Bart Van Assche <bvanass...@acm.org> --- Same problem with konsole 17.04.1 on xfce. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 356374] Assertion 'DRD_(g_threadinfo)[tid].pt_threadid != INVALID_POSIX_THREADID' failed
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.
[valgrind] [Bug 374414] unlocking mutex before calling notify_one/all on condition variable triggers an error
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 that loop the wake-up could still be missed. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 374414] unlocking mutex before calling notify_one/all on condition variable triggers an error
https://bugs.kde.org/show_bug.cgi?id=374414
Bart Van Assche <bvanass...@acm.org> changed:
What|Removed |Added
CC||bvanass...@acm.org
Resolution|--- |INVALID
Status|UNCONFIRMED |RESOLVED
--- Comment #2 from Bart Van Assche <bvanass...@acm.org> ---
Why is this behavior considered to be a bug? Not holding the associated mutex
around pthread_cond_signal() may lead to missed wakeups. It is easy to see in
the example on http://en.cppreference.com/w/cpp/thread/condition_variable that
a wakeup may be missed. Inserting a call to sleep() after
std::unique_lock lk(m) and before cv.wait(lk, []{return
processed;}) will cause the wakeup not to be noticed.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 373166] drd and helgrind will crash wth vex amd64->IR: unhandled instruction bytes 0xFF 0xFF 0x48 0x85 0xC0 0x74 0x8 0x4D 0x89 0xE7
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 reports an unhandled instruction. Have you tried to disassemble the executable with objdump? If not, can you do that and post here the disassembly for the unhandled instruction bytes? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 373166] drd and helgrind will crash wth vex amd64->IR: unhandled instruction bytes 0xFF 0xFF 0x48 0x85 0xC0 0x74 0x8 0x4D 0x89 0xE7
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.
[valgrind] [Bug 373166] drd and helgrind will crash wth vex amd64->IR: unhandled instruction bytes 0xFF 0xFF 0x48 0x85 0xC0 0x74 0x8 0x4D 0x89 0xE7
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.html#faq.msgdeath. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 352395] Please provide SVN revision info in --version
https://bugs.kde.org/show_bug.cgi?id=352395 Bart Van Assche <bvanass...@acm.org> changed: What|Removed |Added CC||bvanass...@acm.org --- Comment #19 from Bart Van Assche <bvanass...@acm.org> --- Although it's not a compiler, the following tool is very convenient for checking the syntax of shell scripts: https://github.com/koalaman/shellcheck. I build and install it as follows: git clone https://github.com/koalaman/shellcheck cd shellcheck cabal update cabal install cabal-install cabal install -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 363740] Possible data race in vgPlain_amd64_linux_REDIR_FOR_vgettimeofday
https://bugs.kde.org/show_bug.cgi?id=363740 Bart Van Assche <bvanass...@acm.org> changed: What|Removed |Added Assignee|jsew...@acm.org |bugzilla@poradnik-webmaster ||a.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 363740] Possible data race in vgPlain_amd64_linux_REDIR_FOR_vgettimeofday
https://bugs.kde.org/show_bug.cgi?id=363740 Bart Van Assche <bvanass...@acm.org> changed: What|Removed |Added CC||bvanass...@acm.org --- Comment #1 from Bart Van Assche <bvanass...@acm.org> --- Why do you think this is a Valgrind issue and not an issue in your application? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 358478] drd/tests/std_thread.cpp doesn't build with GCC6
https://bugs.kde.org/show_bug.cgi?id=358478 Bart Van Assche <bvanass...@acm.org> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #3 from Bart Van Assche <bvanass...@acm.org> --- Does r15773 fix the compilation issue ? If so, does this change make the regression drd regression tests pass ? If not, what does drd report ? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 358478] drd/tests/std_thread.cpp doesn't build with GCC6
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.
