[valgrind] [Bug 446236] New: Issues with Valgrind 3.8.1 version, after compiler upgrade
https://bugs.kde.org/show_bug.cgi?id=446236 Bug ID: 446236 Summary: Issues with Valgrind 3.8.1 version, after compiler upgrade Product: valgrind Version: 3.8.0 Platform: RedHat RPMs OS: Other Status: REPORTED Severity: major Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: amita1...@gmail.com Target Milestone: --- After below compiler upgrade, we are facing issues with valgrind logs. A process is getting created and seen crashing and then re-created. This is in loop. Please let me know if the new versions are supported? Tool Old Version New Version gcc 4.7.2 (2012-06) 8.2.0 (2018-07) binutils2.23.1 (2012-11)2.32 (2019-02) glibc 2.17 (2012-12) 2.23 (2016-02) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 445627] New: Query on Leak summary
https://bugs.kde.org/show_bug.cgi?id=445627 Bug ID: 445627 Summary: Query on Leak summary Product: valgrind Version: 3.15 SVN Platform: Other OS: Other Status: REPORTED Severity: major Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: amita1...@gmail.com Target Milestone: --- Can you please let us know how to check for memory leak or to print that output again when we need. This is required when we do a 24 hour run on Valgrind and check memory leak after 24 hours. Currently the leak summary gets printed at the very beginning of testing. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 438640] vex x86->IR: unhandled instruction bytes: 0xF2 0xF 0x38 0xF1
https://bugs.kde.org/show_bug.cgi?id=438640 --- Comment #7 from amita dwivedi --- Is it possible to fix in valgrind by applying some patch ? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 438640] vex x86->IR: unhandled instruction bytes: 0xF2 0xF 0x38 0xF1
https://bugs.kde.org/show_bug.cgi?id=438640 --- Comment #5 from amita dwivedi --- 2021-Jun-29+04:17:54.678 card 1-cpu0: ==9231== Your program just tried to execute an instruction that Valgrind 2021-Jun-29+04:17:54.678 card 1-cpu0: ==9231== did not recognise. There are two possible reasons for this. 2021-Jun-29+04:17:54.678 card 1-cpu0: ==9231== 1. Your program has a bug and erroneously jumped to a non-code 2021-Jun-29+04:17:54.678 card 1-cpu0: ==9231==location. If you are running Memcheck and you just saw a 2021-Jun-29+04:17:54.678 card 1-cpu0: ==9231==warning about a bad jump, it's probably your program's fault. 2021-Jun-29+04:17:54.678 card 1-cpu0: ==9231== 2. The instruction is legitimate but Valgrind doesn't handle it, 2021-Jun-29+04:17:54.678 card 1-cpu0: ==9231==i.e. it's Valgrind's fault. If you think this is the case or 2021-Jun-29+04:17:54.678 card 1-cpu0: ==9231==you are not sure, please let us know and we'll try to fix it. 2021-Jun-29+04:17:54.678 card 1-cpu0: ==9231== Either way, Valgrind will now raise a SIGILL signal which will 2021-Jun-29+04:17:54.678 card 1-cpu0: ==9231== probably kill your program. 2021-Jun-29+04:17:54.678 card 1-cpu0: ==9231== 2021-Jun-29+04:17:54.678 card 1-cpu0: ==9231== Process terminating with default action of signal 4 (SIGILL): dumping core 2021-Jun-29+04:17:54.678 card 1-cpu0: ==9231== Illegal opcode at address 0x9C7BEA8 2021-Jun-29+04:17:54.678 card 1-cpu0: ==9231==at 0x9C7BEA8: clib_bihash_add_del_40_8_32 (smmintrin.h:815) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 438640] vex x86->IR: unhandled instruction bytes: 0xF2 0xF 0x38 0xF1
https://bugs.kde.org/show_bug.cgi?id=438640 --- Comment #4 from amita dwivedi --- Could you please let me know if there is a way to fix the crash while sending traffic with valgrind enabled. vex x86->IR: unhandled instruction bytes: 0xF2 0xF 0x38 0xF1 valgrind: Unrecognised instruction at address 0x9c7bea8. at 0x9C7BEA8: clib_bihash_add_del_40_8_32 (smmintrin.h:815) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 438647] Not getting memory leak summary
https://bugs.kde.org/show_bug.cgi?id=438647 --- Comment #2 from amita dwivedi --- Thanks. However I am not disabling leak checks but still not getting any memory leak summary. Wondering what could be the scenarios when memory leak summary is not generated in logs. I am getting below valgrind logs Conditional jump or move depends on uninitialised value(s) at 0xABCDEF: policy_status (.c: 1189) by 0xBCDEFG: requests (.c:11340) Invalid read of size 4 at 0xBBB: Open_state (yy.c:413) by 0xCC: calling_function (yy.c:11144) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 438640] vex x86->IR: unhandled instruction bytes: 0xF2 0xF 0x38 0xF1
https://bugs.kde.org/show_bug.cgi?id=438640 --- Comment #2 from amita dwivedi --- Is it Valgrind doesn't support these instructions? How we can fix it to avoid crash -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 438647] Not getting memory leak summary
https://bugs.kde.org/show_bug.cgi?id=438647 amita dwivedi changed: What|Removed |Added Summary|Not getting leak summary|Not getting memory leak ||summary -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 438647] New: Not getting leak summary
https://bugs.kde.org/show_bug.cgi?id=438647 Bug ID: 438647 Summary: Not getting leak summary Product: valgrind Version: 3.15 SVN Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: amita1...@gmail.com Target Milestone: --- SUMMARY I am not getting leak summary when executing valgrind.Please let me know in which scenarios/cases leak summary does'nt generate. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 438640] Getting illegal instruction when sending traffic and dumping core
https://bugs.kde.org/show_bug.cgi?id=438640 amita dwivedi changed: What|Removed |Added Summary|Getting illegal instruction |Getting illegal instruction |when sending traffic and|when sending traffic and |duping core |dumping core -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 438640] New: Getting illegal instruction when sending traffic and duping core
https://bugs.kde.org/show_bug.cgi?id=438640 Bug ID: 438640 Summary: Getting illegal instruction when sending traffic and duping core Product: valgrind Version: 3.15 SVN Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: amita1...@gmail.com Target Milestone: --- SUMMARY Getting below error when running valgrind while sending traffic. vex x86->IR: unhandled instruction bytes: 0xF2 0xF 0x38 0xF1 valgrind: Unrecognised instruction at address 0xABCDE8. at 0xABCDE8: clib_bihash_add_del_40_8_32 (smmintrin.h:815) Process terminating with default action of signal 4 (SIGILL): dumping core Illegal opcode at address 0xABCDE8 STEPS TO REPRODUCE 1. Bring up the subscriber 2. Send traffic by ping 3. Crash will be observed OBSERVED RESULT Crash EXPECTED RESULT It should not crash SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: : Linux (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
