[plasma-browser-integration] [Bug 488653] plasma-browser-integration-host crashes in Firefox 127.0 after upgrade to Plasma 6.1
https://bugs.kde.org/show_bug.cgi?id=488653 Shantanu Tushar changed: What|Removed |Added CC||shant...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 474711] (in)dependent muting
https://bugs.kde.org/show_bug.cgi?id=474711 Shantanu Tushar changed: What|Removed |Added Product|plasma-mediacenter |Elisa Assignee|shant...@kde.org|matthieu_gall...@yahoo.fr Component|MediaPlayer |general -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448751] Media Player Closes When Switching Songs in Music Playlists
https://bugs.kde.org/show_bug.cgi?id=448751 Shantanu Tushar changed: What|Removed |Added Version|5.23.5 |5.23.4 CC||shant...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448751] Media Player Closes When Switching Songs in Music Playlists
https://bugs.kde.org/show_bug.cgi?id=448751 Shantanu Tushar changed: What|Removed |Added CC||plasma-b...@kde.org Component|MediaPlayer |Media Player Product|plasma-mediacenter |plasmashell Target Milestone|--- |1.0 Version|unspecified |5.23.5 Assignee|shant...@kde.org|k...@privat.broulik.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 421856] KWallet does not accept correct password
https://bugs.kde.org/show_bug.cgi?id=421856 --- Comment #11 from Shantanu Tushar --- I can confirm that an upgrade to libkf5wallet5 version 5.71.0-0xneon+18.04+bionic+build49u fixed the problem. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 421856] KWallet does not accept correct password
https://bugs.kde.org/show_bug.cgi?id=421856 Shantanu Tushar changed: What|Removed |Added CC||shant...@kde.org --- Comment #8 from Shantanu Tushar --- I hit the same issue when I upgraded Neon User Edition today. I can reproduce the issue in A VM as well: 1. Install Neon from an older ISO (I used neon-user-20190919-1119.iso) 2. Setup kdewallet with one application (chromium in my case) 3. sudo apt full-upgrade 4. kdewallet no longer accepts my password (I had used empty password for this test) Upgrade log (grep'd to kwallet and upgrade): 2020-06-16 10:17:54 upgrade libkf5wallet-bin:amd64 5.62.0-0xneon+18.04+bionic+build28 5.71.0-0xneon+18.04+bionic+build47 2020-06-16 10:17:55 upgrade libkf5wallet5:amd64 5.62.0-0xneon+18.04+bionic+build28 5.71.0-0xneon+18.04+bionic+build47 2020-06-16 10:17:55 upgrade libkf5wallet-data:all 5.62.0-0xneon+18.04+bionic+build28 5.71.0-0xneon+18.04+bionic+build47 2020-06-16 10:17:57 upgrade libkwalletbackend5-5:amd64 5.62.0-0xneon+18.04+bionic+build28 5.71.0-0xneon+18.04+bionic+build47 -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 391425] Missing support for copying message text
https://bugs.kde.org/show_bug.cgi?id=391425 Shantanu Tushar changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Shantanu Tushar --- Fixed by https://commits.kde.org/ruqola/62017fc7c778fbc549bc0343bc650761e12f5b8b -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 391425] Missing support for copying message text
https://bugs.kde.org/show_bug.cgi?id=391425 Shantanu Tushar changed: What|Removed |Added CC||shant...@kde.org --- Comment #2 from Shantanu Tushar --- I have submitted a patch for this at https://phabricator.kde.org/D29690 Has been few years since I submitted a patch to a KDE project, I hope I didn't miss something obvious in the review request :) -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 353819] Yellow notes have barely visible icons under Breeze Dark
https://bugs.kde.org/show_bug.cgi?id=353819 Tushar Kant changed: What|Removed |Added CC||tusharkan...@gmail.com --- Comment #10 from Tushar Kant --- Hi! Just chiming in to say it's still here in 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404279] New: Plasma crashed after using the show desktop button
https://bugs.kde.org/show_bug.cgi?id=404279 Bug ID: 404279 Summary: Plasma crashed after using the show desktop button Product: kwin Version: 5.14.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: tusharpande...@gmail.com Target Milestone: --- Application: kwin_x11 (5.14.5) Qt Version: 5.12.1 Frameworks Version: 5.55.0 Operating System: Linux 4.20.7-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: I had atom, konsole, okular open all snapped to sides and corners The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3079a2e840 (LWP 1084))] Thread 9 (Thread 0x7f2fc9d8f700 (LWP 20596)): #0 0x7f3082882d16 in ppoll () at /usr/lib/libc.so.6 #1 0x7f3081428bab in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f308142a08b in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f30813d5b2c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f3081219569 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f307f9b6969 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f308121a96c in () at /usr/lib/libQt5Core.so.5 #7 0x7f30801f9a9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f308288db23 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f3070c59700 (LWP 16015)): #0 0x7f3082882d16 in ppoll () at /usr/lib/libc.so.6 #1 0x7f3081428bab in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f308142a08b in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f30813d5b2c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f3081219569 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f307f9b6969 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f308121a96c in () at /usr/lib/libQt5Core.so.5 #7 0x7f30801f9a9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f308288db23 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f30729c4700 (LWP 7436)): #0 0x7f3082882d16 in ppoll () at /usr/lib/libc.so.6 #1 0x7f3081428bab in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f308142a08b in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f30813d5b2c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f3081219569 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f307f9b6969 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f308121a96c in () at /usr/lib/libQt5Core.so.5 #7 0x7f30801f9a9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f308288db23 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f3061e58700 (LWP 1184)): #0 0x7f30801ffafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3080d0428c in () at /usr/lib/libQt5Script.so.5 #2 0x7f3080d042a9 in () at /usr/lib/libQt5Script.so.5 #3 0x7f30801f9a9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f308288db23 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f3062e5a700 (LWP 1174)): #0 0x7f30801ffafc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f30633f6c84 in () at /usr/lib/dri/i965_dri.so #2 0x7f30633f69a8 in () at /usr/lib/dri/i965_dri.so #3 0x7f30801f9a9d in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f308288db23 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f3071ec6700 (LWP 1140)): #0 0x7f3082882d16 in ppoll () at /usr/lib/libc.so.6 #1 0x7f3081428bab in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f308142a08b in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f30813d5b2c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f3081219569 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f307f9b6969 in () at /usr/lib/libQt5Qml.so.5 #6 0x7f308121a96c in () at /usr/lib/libQt5Core.so.5 #7 0x7f30801f9a9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f308288db23 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f3073bd5700 (LWP 1103)): #0 0x7f3082882d16 in ppoll () at /usr/lib/libc.so.6 #1 0x7f3081428bab in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f308142a08b in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f30813d5b2c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Cor
[valgrind] [Bug 372861] Test pselect_alarm for Bug 359871 seg faults on RHEL 4
https://bugs.kde.org/show_bug.cgi?id=372861 --- Comment #1 from Tushar --- The stack trace after commenting out lines 51 and 54 from the test code pselect_alarm.c and running the compiled binary on RHEL 4 machine cacofonix:/home/tdnair> /opt/gdb-7.9.1/bin/gdb pselect_alarm.EL4 -c core.8357 GNU gdb (GDB) 7.9.1 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-unknown-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from pselect_alarm.EL4...done. warning: core file may not match specified executable file. [New LWP 8357] [New LWP 8358] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/tls/libthread_db.so.1". Core was generated by `./pselect_alarm.EL4'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00382b22e799 in sigprocmask () from /lib64/tls/libc.so.6 (gdb) where #0 0x00382b22e799 in sigprocmask () from /lib64/tls/libc.so.6 #1 0x00382b2c3438 in pselect () from /lib64/tls/libc.so.6 #2 0x00400a2a in main () at pselect_alarm.c:52 -- 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 #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 debug binary for me to try, I will be more than happy to do so -- 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 #11 from Tushar --- Is the above information useful? -- 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 #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 callq 382bf04e68 382bf0a2d6: 49 83 fc ff cmp$0x,%r12 382bf0a2da: 74 23 je 382bf0a2ff 382bf0a2dc: 48 8d 15 3d fe ff fflea-0x1c3(%rip),%rdx# 382bf0a120 <__sem_search> 382bf0a2e3: 48 8d 35 66 a0 10 00lea0x10a066(%rip),%rsi# 382c014350 <__sem_mappings> 382bf0a2ea: 48 89 dfmov%rbx,%rdi 382bf0a2ed: e8 46 ad ff ff callq 382bf05038 382bf0a2f2: 48 85 c0test %rax,%rax 382bf0a2f5: 74 08 je 382bf0a2ff 382bf0a2f7: 4d 89 e7mov%r12,%r15 382bf0a2fa: e9 74 ff ff ff jmpq 382bf0a273 382bf0a2ff: 48 89 dfmov%rbx,%rdi 382bf0a302: e8 71 ad ff ff callq 382bf05078 382bf0a307: e9 67 ff ff ff jmpq 382bf0a273 382bf0a30c: 45 31 c9xor%r9d,%r9d 382bf0a30f: 45 89 f0mov%r14d,%r8d The thing that caught my attention is that data @ 0x382BF0A2F0 seems to be part of callq instruction @ 382bf0a2ed. VEX seems to think it is the start of a new instruction. The disassembly of the test code (sem_open) itself at the are of interest is 400aca: ba f6 0d 40 00 mov$0x400df6,%edx 400acf: be 20 00 00 00 mov$0x20,%esi 400ad4: b8 00 00 00 00 mov$0x0,%eax 400ad9: e8 e2 fd ff ff callq 4008c0 400ade: 48 8d 7d c0 lea-0x40(%rbp),%rdi 400ae2: b9 01 00 00 00 mov$0x1,%ecx 400ae7: ba 80 01 00 00 mov$0x180,%edx 400aec: be c0 00 00 00 mov$0xc0,%esi 400af1: b8 00 00 00 00 mov$0x0,%eax 400af6: e8 25 fe ff ff callq 400920 400afb: 48 89 05 b6 07 20 00mov%rax,0x2007b6(%rip)# 6012b8 400b02: 48 83 3d ae 07 20 00cmpq $0x0,0x2007ae(%rip)# 6012b8 400b09: 00 400b0a: 75 24 jne400b30 400b0c: 48 8d 55 c0 lea-0x40(%rbp),%rdx 400b10: be 10 0e 40 00 mov$0x400e10,%esi 400b15: 48 8b 3d 7c 07 20 00mov0x20077c(%rip),%rdi# 601298 400b1c: b8 00 00 00 00 mov$0x0,%eax 400b21: e8 ea fd ff ff callq 400910 I hope this information helps -- 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 #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 it is very relevant to us. I can help with investigation and testing but some pointers would definitely help. To summarize my findings are The crash only happens with 64 bit drd and helgrind test case. memcheck is OK. 32 bit test cases have not problem with either of the checkers. so I'm wondering if this issue contained inside VEX or do the checkers also have a role to play. Am I on the right track with my thought process? -- 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 #6 from Tushar --- Any help/suggestions on how to proceed? -- 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 #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: 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 Tushar changed: What|Removed |Added Component|drd |vex --- Comment #4 from Tushar --- Thank you for pointing to the right component. Since the error was happening in the context of drd and helgrind, I picked those. -- 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 #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 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 #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 size : 4096 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 4 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl est tm2 cx16 xtpr lahf_lm bogomips: 5323.68 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: glibc version glibc-2.3.4-2.57.x86_64 Running the tests outside valgrind produces no errors Context form /lib64/tls/libpthread-2.3.4.so 382bf0a2d1: e8 92 ab ff ff callq 382bf04e68 382bf0a2d6: 49 83 fc ff cmp$0x,%r12 382bf0a2da: 74 23 je 382bf0a2ff 382bf0a2dc: 48 8d 15 3d fe ff fflea-0x1c3(%rip),%rdx# 382bf0a120 <__sem_search> 382bf0a2e3: 48 8d 35 66 a0 10 00lea0x10a066(%rip),%rsi# 382c014350 <__sem_mappings> 382bf0a2ea: 48 89 dfmov%rbx,%rdi 382bf0a2ed: e8 46 ad ff ff callq 382bf05038 382bf0a2f2: 48 85 c0test %rax,%rax 382bf0a2f5: 74 08 je 382bf0a2ff 382bf0a2f7: 4d 89 e7mov%r12,%r15 382bf0a2fa: e9 74 ff ff ff jmpq 382bf0a273 382bf0a2ff: 48 89 dfmov%rbx,%rdi 382bf0a302: e8 71 ad ff ff callq 382bf05078 382bf0a307: e9 67 ff ff ff jmpq 382bf0a273 382bf0a30c: 45 31 c9xor%r9d,%r9d 382bf0a30f: 45 89 f0mov%r14d,%r8d -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 373166] New: 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 Bug ID: 373166 Summary: drd and helgrind will crash wth vex amd64->IR: unhandled instruction bytes 0xFF 0xFF 0x48 0x85 0xC0 0x74 0x8 0x4D 0x89 0xE7 Product: valgrind Version: 3.12.0 Platform: RedHat RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: drd Assignee: bvanass...@acm.org Reporter: ntus...@yahoo.com Target Milestone: --- The tests drd/tests/sem_open, sem_open2, sem_open3 and sem_open_traced all crash with unhandled instruction error ==14999== drd, a thread error detector ==14999== Copyright (C) 2006-2015, and GNU GPL'd, by Bart Van Assche. ==14999== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info ==14999== Command: ./sem_open -m ==14999== vex amd64->IR: unhandled instruction bytes: 0xFF 0xFF 0x48 0x85 0xC0 0x74 0x8 0x4D 0x89 0xE7 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 ==14999== valgrind: Unrecognised instruction at address 0x382bf0a2f0. ==14999==at 0x382BF0A2F0: check_add_mapping (in /lib64/tls/libpthread-2.3.4.so) ==14999==by 0x4A14EDF: sem_open_intercept (drd_pthread_intercepts.c:1391) ==14999==by 0x4A14EDF: sem_open (drd_pthread_intercepts.c:1398) ==14999==by 0x400AFA: main (sem_open.c:63) ==14999== Your program just tried to execute an instruction that Valgrind ==14999== did not recognise. There are two possible reasons for this. ==14999== 1. Your program has a bug and erroneously jumped to a non-code ==14999==location. If you are running Memcheck and you just saw a ==14999==warning about a bad jump, it's probably your program's fault. ==14999== 2. The instruction is legitimate but Valgrind doesn't handle it, ==14999==i.e. it's Valgrind's fault. If you think this is the case or ==14999==you are not sure, please let us know and we'll try to fix it. ==14999== Either way, Valgrind will now raise a SIGILL signal which will ==14999== probably kill your program. ==14999== ==14999== Process terminating with default action of signal 4 (SIGILL): dumping core ==14999== Illegal opcode at address 0x382BF0A2F0 ==14999==at 0x382BF0A2F0: check_add_mapping (in /lib64/tls/libpthread-2.3.4.so) ==14999==by 0x4A14EDF: sem_open_intercept (drd_pthread_intercepts.c:1391) ==14999==by 0x4A14EDF: sem_open (drd_pthread_intercepts.c:1398) ==14999==by 0x400AFA: main (sem_open.c:63) ==14999== ==14999== For counts of detected and suppressed errors, rerun with: -v ==14999== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) Illegal instruction -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372861] New: Test pselect_alarm for Bug 359871 seg faults on RHEL 4
https://bugs.kde.org/show_bug.cgi?id=372861 Bug ID: 372861 Summary: Test pselect_alarm for Bug 359871 seg faults on RHEL 4 Product: valgrind Version: 3.12 SVN Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: ntus...@yahoo.com Target Milestone: --- Linux cacofonix 2.6.9-89.0.9.ELsmp #1 SMP Wed Aug 19 08:06:10 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux The crash occurs at line assert(pselect(0, NULL, NULL, NULL, NULL, (sigset_t *)12) == -1); RHEL 4 does not handle bad address by returning EFAULT If the goal is to have pselect fail, can the test be replace with assert(pselect(-1, NULL, NULL, NULL, NULL, NULL) == -1); assert(errno == EINVAL); These changes work on RHEL 4, 5 and 6. -- You are receiving this mail because: You are watching all bug changes.
