https://bugs.kde.org/show_bug.cgi?id=373166
--- Comment #13 from Tushar ---
Julian,
Thanks for getting back. I tried to find out what is happening and didn't make
much headway. The problem can be reliably reproduced on an RHEL 4 system. So
if you want me to instrument something or if you have
https://bugs.kde.org/show_bug.cgi?id=373166
Julian Seward changed:
What|Removed |Added
CC||jsew...@acm.org
--- Comment #12 from Julian Sew
https://bugs.kde.org/show_bug.cgi?id=373166
--- Comment #11 from Tushar ---
Is the above information useful?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373166
--- Comment #10 from Tushar ---
Based on the crash information, I did disassemble the library in question
(/lib64/tls/libpthread-2.3.4.so) and looked at the instructions at the address
0x382BF0A2F0. The instructions are
382bf0a2d1: e8 92 ab ff ff
https://bugs.kde.org/show_bug.cgi?id=373166
--- Comment #9 from Bart Van Assche ---
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
https://bugs.kde.org/show_bug.cgi?id=373166
--- Comment #8 from Tushar ---
Our computers are part of a $20+ million semiconductor capital equipment whose
annual maintenance contract itself runs into hundreds of thousands of dollars a
year. So we can't drop support for legacy systems easily. So
https://bugs.kde.org/show_bug.cgi?id=373166
--- Comment #7 from Bart Van Assche ---
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 #6 from Tushar ---
Any help/suggestions on how to proceed?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=373166
--- Comment #5 from Tushar ---
When running memcheck, this error does NOT occur. Does VEX instrument
libraries differently depending on the checker used?
The same problem persists in version 3.8.0 and 3.11.0
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=373166
Tushar changed:
What|Removed |Added
Component|drd |vex
--- Comment #4 from Tushar ---
Thank you for poin
https://bugs.kde.org/show_bug.cgi?id=373166
--- Comment #3 from Bart Van Assche ---
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
https://bugs.kde.org/show_bug.cgi?id=373166
--- Comment #2 from Tushar ---
This problem only seems to be happening with glibc 2.3.4 which is part of
RHEL4.
glibc 2.5 (RHEL5) and glibc 2.12 (RHEL 6) don't exhibit this problem
--
You are receiving this mail because:
You are watching all bug chang
https://bugs.kde.org/show_bug.cgi?id=373166
--- Comment #1 from Tushar ---
cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Xeon(R) CPU X5355 @ 2.66GHz
stepping: 7
cpu MHz : 2660.004
cache si
13 matches
Mail list logo
