1 2 Bugs reported after the release of 3.4.1. Not sure what happened to 3 any record of bugs reported after the release of 3.4.0. Oh well. 4 5 For ref: 6 7 (3.4.1.RC1: 24 Feb 2009, vex r1884, valgrind r9253). 8 (3.4.1: 28 Feb 2009, vex r1884, valgrind r9293). 9 10 ------------------- 11 12 185128 Helgrind: hg_main.c:3860 (hg_handle_client_request): 13 Assertion 'found' failed. 14 15 185499 testcase usability kde brainfuck 16 17 185517 Wrong write detection 18 19 185794 "WARNING: unhandled syscall: 285" (fallocate) on x86_64 20 in several tools 21 22 185801 exp-ptrcheck: evaluate_Dwarf3_Expr: unhandled DW_OP_ 0x93 23 24 185816 Valgrind is unable to handle debug info for files with 25 split debug info that are prelinked afterwards 26 27 186238 bbToIR_AMD64: disInstr miscalculated next %rip 28 29 186248 Support full AMD floating-point implementation. 30 31 186507 exp-ptrcheck unhandled syscalls prctl, etc. 32 33 186790 Suppression pattern used for leaks are not reported 34 35 186796 Symbols with length>200 in suppression files are ignored 36 37 157154 documentation (leak-resolution doc speaks about num-callers 38 def=4) + what is a loss record 39 40 186963 Report mutexes humanic names 41 42 187043 sched_getcpu() produces Segmentation Fault 43 44 187048 mutex PTHREAD_PROCESS_SHARED attribute missinterpretation 45 46 187416 support for __NR_{setregid,setreuid,setresuid} in 47 exp-ptrcheck 48 49 187680 valgrind: the 'impossible' happened (probably invalid) 50 51 187760 valgrind: the 'impossible' happened: VG_(arena_memalign) 52 53 188038 Helgrind internal error 54 55 188046 bashisms in the configure script 56 57 188127 vex amd64->IR: unhandled instruction bytes: 0xF0 0xF 0xB0 0xA 58 (ancient cmpxchg stuff, probably invalid now) 59 60 188161 valgrind --track-origins=yes asserts (transient trunk 61 stuff, now fixed?) 62 63 188248 pthread_cleanup_push, pthread_rwlock_unlock, assertion 64 fail "!lock->heldBy" 65 66 188258 javascript fragment gives different result under valgrind 67 (requires SSSE3 exns; cant easily fix?) 68 69 188427 Add support for epoll_create1 (with patch) 70 71 188530 Support for SIOCGSTAMPNS 72 73 188560 Include valgrind.spec in the tarball 74 75 188572 Valgrind on Mac should suppress setenv() mem leak 76 77 188656 valgrind doesn't build on x86_64 machine (INVALID) 78 79 188657 Massif: ms_main.c:1700 (update_stack_stats): Assertion 80 'stacks_szB >= -stack_szB_delta' failed 81 82 188735 Cachegrind fails to produce any output on java apps 83 84 188969 thread's stack is not computed correctly 85 86 188984 Data corruption for returned from function long double 87 (fp grumblings) 88 89 189028 impossible happend in unlinkBlock (m_mallocfree.c:206) 90 (usual memory corruption) -- invalid 91 92 189054 Valgrind fails to build because of duplicate non-local 93 asm labels 94 95 189143 crash when running using wine to run vcsetup.exe under 96 valgrind 97 98 189183 valgrind core dump on aix5.3 platform 99 100 189232 Illegal opcode - unhandled instruction bytes: 0xCB 0x55 101 0x8B 0xEC 102 103 189361 Cache simulation slightly wrong 104 105 189661 Valgrind on Mac hangs on a race-condition 106 107 189737 vex amd64->IR: unhandled instruction bytes: 0xAC (lods) 108 109 189762 epoll_create syscall not handled (in ptrcheck) 110 111 189763 drd assertion failure: s_threadinfo[tid].is_recording 112 113 190219 unhandled syscall: 328 (x86-linux, __NR_eventfd2 ?) 114 115 190390 Allow to set the number of frames for helgrind conflicts 116 117 190391 okular crashes helgrind 118 ==181394 119 120 190429 Valgrind reports lost of errors in ld.so with x86_64 121 2.9.90 glibc 122 123 (next 2 are wine-specific) 124 190660 False warnings for _strlen 125 190675 Spurious error "Wrong time stamp of .PDB file" 126 127 190820 No debug information on powerpc-linux 128 129 (-- 27 Apr 09 --) 130 131
