[valgrind] [Bug 371065] www: add CfP for FOSDEM 2017 in valgrind.org NEWS section

https://bugs.kde.org/show_bug.cgi?id=371065 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are

[valgrind] [Bug 371065] New: www: add CfP for FOSDEM 2017 in valgrind.org NEWS section

https://bugs.kde.org/show_bug.cgi?id=371065 Bug ID: 371065 Summary: www: add CfP for FOSDEM 2017 in valgrind.org NEWS section Product: valgrind Version: unspecified Platform: unspecified OS: other

[valgrind] [Bug 370941] Investigate using new VG_(HT_remove_at_Iter)() at other places in memcheck

https://bugs.kde.org/show_bug.cgi?id=370941 Ivo Raisr changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|---

[valgrind] [Bug 370941] Investigate using new VG_(HT_remove_at_Iter)() at other places in memcheck

https://bugs.kde.org/show_bug.cgi?id=370941 Ivo Raisr changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[valgrind] [Bug 370941] Investigate using new VG_(HT_remove_at_Iter)() at other places in memcheck

https://bugs.kde.org/show_bug.cgi?id=370941 Ivo Raisr changed: What|Removed |Added Depends on||369468 -- You are receiving this

[valgrind] [Bug 369468] Implement HT_remove_at_Iter to avoid quadratic auto free pool algorithm

https://bugs.kde.org/show_bug.cgi?id=369468 Ivo Raisr changed: What|Removed |Added Blocks||370941 -- You are receiving this

[valgrind] [Bug 370941] Investigate using new VG_(HT_remove_at_Iter)() at other places in memcheck

https://bugs.kde.org/show_bug.cgi?id=370941 Ivo Raisr changed: What|Removed |Added Assignee|jsew...@acm.org |iv...@ivosh.net

[valgrind] [Bug 370941] New: Investigate using new VG_(HT_remove_at_Iter)() at other places in memcheck

https://bugs.kde.org/show_bug.cgi?id=370941 Bug ID: 370941 Summary: Investigate using new VG_(HT_remove_at_Iter)() at other places in memcheck Product: valgrind Version: 3.12 SVN Platform: Compiled Sources

[valgrind] [Bug 370028] Reduce the number of compiler warnings on MIPS platforms

https://bugs.kde.org/show_bug.cgi?id=370028 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net --- Comment #8

[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

https://bugs.kde.org/show_bug.cgi?id=369209 --- Comment #8 from Ivo Raisr --- Hi Mark, the new test case works ok (I am able to simulate the problem on Solaris) with 'make one component inaccessible'. Please include "string[s].h" for proper strlen declaration. My apologies it

[valgrind] [Bug 367995] Integration of memcheck with custom memory allocator

https://bugs.kde.org/show_bug.cgi?id=367995 Ivo Raisr changed: What|Removed |Added Latest Commit||15985 --- Comment #22 from Ivo

[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

https://bugs.kde.org/show_bug.cgi?id=369209 --- Comment #6 from Ivo Raisr --- Yes, cwd of another process can be removed; but as usually the process holds a reference on it: "If the directory's link count becomes zero and no process has the directory open,

[valgrind] [Bug 367995] Integration of memcheck with custom memory allocator

https://bugs.kde.org/show_bug.cgi?id=367995 --- Comment #21 from Ivo Raisr --- Ruurd, would you like to provide an implementation of VG_(HT_remove_at_Iter)()? If yes, please create a new bug for tracking it. -- You are receiving this mail because: You are watching all bug

[valgrind] [Bug 367995] Integration of memcheck with custom memory allocator

https://bugs.kde.org/show_bug.cgi?id=367995 Ivo Raisr changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

https://bugs.kde.org/show_bug.cgi?id=369209 --- Comment #4 from Ivo Raisr --- Hi Mark, I get this compilation warning on Solaris: nocwd.c: In function ‘main’: nocwd.c:28:3: warning: missing sentinel in function call [-Wformat=] execlp ("echo", "echo", "Hello", "World",

[valgrind] [Bug 367995] Integration of memcheck with custom memory allocator

https://bugs.kde.org/show_bug.cgi?id=367995 --- Comment #17 from Ivo Raisr --- I will take care of the integration if Philippe is ok with it. Things which need to be done: - update NEWS - mark the filter script as executable for svn - mark the compiled binary as ignored for svn

[valgrind] [Bug 369209] valgrind loops and eats up all memory (very slowly) when the current working directory doesn't exist.

https://bugs.kde.org/show_bug.cgi?id=369209 --- Comment #3 from Ivo Raisr --- Will do. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 367995] Integration of memcheck with custom memory allocator

https://bugs.kde.org/show_bug.cgi?id=367995 --- Comment #12 from Ivo Raisr --- Thank you for your review, Julian. 1) I will let Ruurd comment on this. 2) a+b is addressed in the new patch v3 (attached). 3) I was not able to come up with an efficient way how to express this

[valgrind] [Bug 367995] Integration of memcheck with custom memory allocator

https://bugs.kde.org/show_bug.cgi?id=367995 Ivo Raisr changed: What|Removed |Added Attachment #101103|0 |1 is obsolete|

[valgrind] [Bug 367995] Integration of memcheck with custom memory allocator

https://bugs.kde.org/show_bug.cgi?id=367995 --- Comment #8 from Ivo Raisr --- The attached patch is ready to land. Regression tests pass on x86/Linux, amd64/Linux (Ubuntu), x86/Solaris and amd64/Solaris. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 367995] Integration of memcheck with custom memory allocator

https://bugs.kde.org/show_bug.cgi?id=367995 Ivo Raisr changed: What|Removed |Added Attachment #100849|0 |1 is obsolete|

[valgrind] [Bug 368507] valgrind throws std::bad_alloc on memory allocations larger than 34255421416 bytes

https://bugs.kde.org/show_bug.cgi?id=368507 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net --- Comment #4

[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal

https://bugs.kde.org/show_bug.cgi?id=361615 --- Comment #10 from Ivo Raisr --- As Philippe pointed out, there is a problem with the existing attachment. Please have a look what is there inside and re-attach. -- You are receiving this mail because: You are watching all bug

[valgrind] [Bug 367995] Integration of memcheck with custom memory allocator

https://bugs.kde.org/show_bug.cgi?id=367995 --- Comment #2 from Ivo Raisr --- Also when running the newly introduced regressions tests, I encountered this failure: $ cat memcheck/tests/leak-autofreepool-5.stderr.diff --- leak-autofreepool-5.stderr.exp 2016-08-31

[valgrind] [Bug 367995] Integration of memcheck with custom memory allocator

https://bugs.kde.org/show_bug.cgi?id=367995 Ivo Raisr changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0

[valgrind] [Bug 367995] Integration of memcheck with custom memory allocator

https://bugs.kde.org/show_bug.cgi?id=367995 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net

[valgrind] [Bug 364413] pselect sycallwrapper mishandles NULL sigmask

https://bugs.kde.org/show_bug.cgi?id=364413 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net --- Comment #4

[valgrind] [Bug 345307] Warning about "still reachable" memory when using libstdc++ from gcc 5

https://bugs.kde.org/show_bug.cgi?id=345307 --- Comment #27 from Ivo Raisr --- Status: - Fixed for libstdc++ from gcc 6. - Not fixed for libstdc++ from gcc 5 because they won't accept a new public symbol there. You can use a workaround from comment #15. -- You are receiving

[valgrind] [Bug 360378] arm64: Unhandled instruction 0x5E280844 (sha1h s4, s2)

https://bugs.kde.org/show_bug.cgi?id=360378 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are

[valgrind] [Bug 364058] array overruns are not detected

https://bugs.kde.org/show_bug.cgi?id=364058 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net --- Comment #1

[valgrind] [Bug 280974] generated suppressions based on the origin of uninitialized memory

https://bugs.kde.org/show_bug.cgi?id=280974 --- Comment #6 from Ivo Raisr --- Anyway, patches are welcome! -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 303877] valgrind doesn't support compressed debuginfo sections.

https://bugs.kde.org/show_bug.cgi?id=303877 Ivo Raisr changed: What|Removed |Added Latest Commit|15868 |15869 --- Comment #40 from Ivo

[valgrind] [Bug 303877] valgrind doesn't support compressed debuginfo sections.

https://bugs.kde.org/show_bug.cgi?id=303877 Ivo Raisr changed: What|Removed |Added Latest Commit||15868 Resolution|---

[valgrind] [Bug 362009] Valgrind dumps core on unimplemented functionality before threads are created

https://bugs.kde.org/show_bug.cgi?id=362009 Ivo Raisr changed: What|Removed |Added Latest Commit||15867

[valgrind] [Bug 303877] valgrind doesn't support compressed debuginfo sections.

https://bugs.kde.org/show_bug.cgi?id=303877 --- Comment #38 from Ivo Raisr --- Dilyan Palauzov reports duplicate line in configure.ac: AC_CHECK_TYPES([Elf32_Chdr, Elf64_Chdr], [], [], [[#include ]]) -- You are receiving this mail because: You are

[valgrind] [Bug 362009] Valgrind dumps core on unimplemented functionality before threads are created

https://bugs.kde.org/show_bug.cgi?id=362009 --- Comment #4 from Ivo Raisr --- You are right, Philippe, that's very good remark. I have attached new patch. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 362009] Valgrind dumps core on unimplemented functionality before threads are created

https://bugs.kde.org/show_bug.cgi?id=362009 Ivo Raisr changed: What|Removed |Added Attachment #98481|0 |1 is obsolete|

[valgrind] [Bug 362009] Valgrind dumps core on unimplemented functionality before threads are created

https://bugs.kde.org/show_bug.cgi?id=362009 --- Comment #1 from Ivo Raisr --- Created attachment 98481 --> https://bugs.kde.org/attachment.cgi?id=98481=edit proposed patch The patch consists mainly of whitespace changes due to different indentation. -- You are receiving

[valgrind] [Bug 362009] Valgrind dumps core on unimplemented functionality before threads are created

https://bugs.kde.org/show_bug.cgi?id=362009 Ivo Raisr changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[valgrind] [Bug 362009] Valgrind dumps core on unimplemented functionality before threads are created

https://bugs.kde.org/show_bug.cgi?id=362009 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net

[valgrind] [Bug 362009] New: Valgrind dumps core on unimplemented functionality before threads are created

https://bugs.kde.org/show_bug.cgi?id=362009 Bug ID: 362009 Summary: Valgrind dumps core on unimplemented functionality before threads are created Product: valgrind Version: 3.12 SVN Platform: Compiled Sources

[valgrind] [Bug 361926] Unhandled Solaris syscall: sysfs(84)

https://bugs.kde.org/show_bug.cgi?id=361926 Ivo Raisr changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|---

[valgrind] [Bug 361926] Unhandled Solaris syscall: sysfs(84)

https://bugs.kde.org/show_bug.cgi?id=361926 Ivo Raisr changed: What|Removed |Added Summary|unhandled x86-solaris |Unhandled Solaris syscall:

[valgrind] [Bug 361926] unhandled x86-solaris syscall: 84

https://bugs.kde.org/show_bug.cgi?id=361926 Ivo Raisr changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC|

[valgrind] [Bug 303877] valgrind doesn't support compressed debuginfo sections.

https://bugs.kde.org/show_bug.cgi?id=303877 --- Comment #36 from Ivo Raisr --- Thank you, Aleksandar, for patches rev2. I have attached rev3 and run it on amd64/Solaris 12 and amd64/Ubuntu. Regression testing went ok. Actually Solaris 12 has working combination of gcc 5.3 and

[valgrind] [Bug 303877] valgrind doesn't support compressed debuginfo sections.

https://bugs.kde.org/show_bug.cgi?id=303877 Ivo Raisr changed: What|Removed |Added Attachment #97607|0 |1 is obsolete|

[valgrind] [Bug 303877] valgrind doesn't support compressed debuginfo sections.

https://bugs.kde.org/show_bug.cgi?id=303877 Ivo Raisr changed: What|Removed |Added Assignee|jsew...@acm.org |iv...@ivosh.net -- You are

[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal

https://bugs.kde.org/show_bug.cgi?id=361615 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are

[valgrind] [Bug 301830] MultiThreadedV (mtV): improve Valgrind so that it runs multiple threads in parallel

https://bugs.kde.org/show_bug.cgi?id=301830 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are

[valgrind] [Bug 354809] Error message for unsupported platform is unhelpful

https://bugs.kde.org/show_bug.cgi?id=354809 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are

[valgrind] [Bug 356174] Enhance the embedded gdbserver to allow LLDB to use it

https://bugs.kde.org/show_bug.cgi?id=356174 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are

[valgrind] [Bug 356273] conserve memory by merging adjacent DiLoc entries in the debug info location table

https://bugs.kde.org/show_bug.cgi?id=356273 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are

[valgrind] [Bug 356374] Assertion 'DRD_(g_threadinfo)[tid].pt_threadid != INVALID_POSIX_THREADID' failed

https://bugs.kde.org/show_bug.cgi?id=356374 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are

[valgrind] [Bug 356457] valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)' failed.

https://bugs.kde.org/show_bug.cgi?id=356457 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are

[valgrind] [Bug 358213] helgrind/drd bar_bad testcase hangs with new glibc pthread barrier implementation

https://bugs.kde.org/show_bug.cgi?id=358213 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are

[valgrind] [Bug 359181] Buffer Overflow during Demangling

https://bugs.kde.org/show_bug.cgi?id=359181 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are

[valgrind] [Bug 359249] valgrind unable to load 64-bit linux executable linked with -mcmodel=medium

https://bugs.kde.org/show_bug.cgi?id=359249 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are

[valgrind] [Bug 359524] bt, btc, btr and bts instruction improperly translated by VEX on x86-64

https://bugs.kde.org/show_bug.cgi?id=359524 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are

[valgrind] [Bug 360557] helgrind reports data race which I can't see (involves rwlocks)

https://bugs.kde.org/show_bug.cgi?id=360557 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are

[valgrind] [Bug 345307] Warning about "still reachable" memory when using libstdc++ from gcc 5

https://bugs.kde.org/show_bug.cgi?id=345307 --- Comment #26 from Ivo Raisr --- Followup fix for x86 architecture: SVN r15854. Failed test case was memcheck/tests/addressable built as 32-bit executable which showed: Conditional jump or move depends on uninitialised value(s)

[valgrind] [Bug 360749] kludge for multiple .rodata sections on Solaris no longer needed

https://bugs.kde.org/show_bug.cgi?id=360749 Ivo Raisr changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 353802] ELF debug info reader confused with multiple .rodata sections

https://bugs.kde.org/show_bug.cgi?id=353802 --- Comment #9 from Ivo Raisr --- Reverted by bug #360749. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 361504] dlopen()/dlclose() and shared object usage check

https://bugs.kde.org/show_bug.cgi?id=361504 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are

[valgrind] [Bug 354392] unhandled amd64-solaris syscall: 171

https://bugs.kde.org/show_bug.cgi?id=354392 Ivo Raisr changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[valgrind] [Bug 353920] unhandled amd64-solaris syscall: 170

https://bugs.kde.org/show_bug.cgi?id=353920 Ivo Raisr changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[valgrind] [Bug 353917] unhandled amd64-solaris syscall fchdir(120)

https://bugs.kde.org/show_bug.cgi?id=353917 Ivo Raisr changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 353398] WARNING: unhandled amd64-solaris syscall: 207 whenever I run a C++ binary with Valgrind

https://bugs.kde.org/show_bug.cgi?id=353398 Ivo Raisr changed: What|Removed |Added Assignee|jsew...@acm.org |iv...@ivosh.net -- You are

[valgrind] [Bug 353398] WARNING: unhandled amd64-solaris syscall: 207 whenever I run a C++ binary with Valgrind

https://bugs.kde.org/show_bug.cgi?id=353398 Ivo Raisr changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[valgrind] [Bug 345307] Warning about "still reachable" memory when using libstdc++ from gcc 5

https://bugs.kde.org/show_bug.cgi?id=345307 --- Comment #23 from Ivo Raisr --- Fixed in SVN r15840, for gcc 6. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 345307] Warning about "still reachable" memory when using libstdc++ from gcc 5

https://bugs.kde.org/show_bug.cgi?id=345307 --- Comment #22 from Ivo Raisr --- The first issue is fixed by SVN r15839. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 345307] Warning about "still reachable" memory when using libstdc++ from gcc 5

https://bugs.kde.org/show_bug.cgi?id=345307 --- Comment #21 from Ivo Raisr --- There is some backgroud for memcheck/tests/reach_thread_register: https://bugs.kde.org/show_bug.cgi?id=324227 -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 345307] Warning about "still reachable" memory when using libstdc++ from gcc 5

https://bugs.kde.org/show_bug.cgi?id=345307 --- Comment #20 from Ivo Raisr --- Mark, thank you for review. However I found two problems with the patch (v3): - memcheck/tests/reach_thread_register fails on amd64/Solaris - freeres wrapper is called on Solaris, even if there is no

[valgrind] [Bug 345307] Warning about "still reachable" memory when using libstdc++ from gcc 5

https://bugs.kde.org/show_bug.cgi?id=345307 Ivo Raisr changed: What|Removed |Added Attachment #98117|0 |1 is obsolete|

[valgrind] [Bug 345307] Warning about "still reachable" memory when using libstdc++ from gcc 5

https://bugs.kde.org/show_bug.cgi?id=345307 Ivo Raisr changed: What|Removed |Added Attachment #97556|0 |1 is obsolete|

[valgrind] [Bug 360752] raise the number of reserved fds in m_main.c from 10 to 12

https://bugs.kde.org/show_bug.cgi?id=360752 Ivo Raisr changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|---

[valgrind] [Bug 360752] raise the number of reserved fds in m_main.c from 10 to 12

https://bugs.kde.org/show_bug.cgi?id=360752 --- Comment #4 from Ivo Raisr --- I am glad you found the list useful. However /proc/pid/{cmdline,auxv,psinfo} are *not* fd leaks. See this comment from m_main.c: //--

[valgrind] [Bug 360752] raise the number of reserved fds in m_main.c from 10 to 12

https://bugs.kde.org/show_bug.cgi?id=360752 --- Comment #2 from Ivo Raisr --- Here is a summary of file descriptors owned specifically by Valgrind during gdbserver_tests/nlpasssigalrm test execution, when fork_sys syscall wrapper is executing. 256: S_IFREG:

[valgrind] [Bug 360752] raise the number of reserved fds in m_main.c from 10 to 12

https://bugs.kde.org/show_bug.cgi?id=360752 Ivo Raisr changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0

[valgrind] [Bug 360752] raise the number of reserved fds in m_main.c from 10 to 12

https://bugs.kde.org/show_bug.cgi?id=360752 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are

[valgrind] [Bug 360752] raise the number of reserved fds in m_main.c from 10 to 12

https://bugs.kde.org/show_bug.cgi?id=360752 --- Comment #1 from Ivo Raisr --- Created attachment 97984 --> https://bugs.kde.org/attachment.cgi?id=97984=edit proposed patch -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 360752] New: raise the number of reserved fds in m_main.c from 10 to 12

https://bugs.kde.org/show_bug.cgi?id=360752 Bug ID: 360752 Summary: raise the number of reserved fds in m_main.c from 10 to 12 Product: valgrind Version: 3.12 SVN Platform: Compiled Sources OS: Solaris

[valgrind] [Bug 360752] raise the number of reserved fds in m_main.c from 10 to 12

https://bugs.kde.org/show_bug.cgi?id=360752 Ivo Raisr changed: What|Removed |Added Assignee|jsew...@acm.org |iv...@ivosh.net -- You are

[valgrind] [Bug 360749] kludge for multiple .rodata sections on Solaris no longer needed

https://bugs.kde.org/show_bug.cgi?id=360749 --- Comment #1 from Ivo Raisr --- Created attachment 97982 --> https://bugs.kde.org/attachment.cgi?id=97982=edit proposed patch -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 360749] kludge for multiple .rodata sections on Solaris no longer needed

https://bugs.kde.org/show_bug.cgi?id=360749 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net

[valgrind] [Bug 360749] New: kludge for multiple .rodata sections on Solaris no longer needed

https://bugs.kde.org/show_bug.cgi?id=360749 Bug ID: 360749 Summary: kludge for multiple .rodata sections on Solaris no longer needed Product: valgrind Version: 3.12 SVN Platform: Compiled Sources OS:

[valgrind] [Bug 303877] valgrind doesn't support compressed debuginfo sections.

https://bugs.kde.org/show_bug.cgi?id=303877 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net --- Comment #26

[valgrind] [Bug 79362] Debug info is lost for .so files when they are dlclose'd

https://bugs.kde.org/show_bug.cgi?id=79362 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

https://bugs.kde.org/show_bug.cgi?id=359871 Ivo Raisr changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

https://bugs.kde.org/show_bug.cgi?id=359871 Ivo Raisr changed: What|Removed |Added Attachment #97643|0 |1 is obsolete|

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

https://bugs.kde.org/show_bug.cgi?id=359871 --- Comment #18 from Ivo Raisr --- Thank you for a quick turnaround. I think this should work. As regards the scalar test, if you are not able to get it working with high confidence then we should probably leave it alone. I will

[valgrind] [Bug 345307] Warning about "still reachable" memory when using libstdc++ from gcc 5

https://bugs.kde.org/show_bug.cgi?id=345307 --- Comment #14 from Ivo Raisr --- My apologies, we were talking about different things which just now I realized. Now I understand you are talking about VG_USERREQ__LIBC_FREERES_DONE client request whereas I was talking about

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

https://bugs.kde.org/show_bug.cgi?id=359871 --- Comment #16 from Ivo Raisr --- Please could you also move the test for failed pselect into memcheck/tests/x86-linux/scalar.c where it truly belongs. See its header. Thanks a lot! -- You are receiving this mail because: You are

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

https://bugs.kde.org/show_bug.cgi?id=359871 --- Comment #15 from Ivo Raisr --- Thank you for quick fix and analysis. Yes, indeed, changing args for failed syscall wrapper is not allowed. I wonder why you need to explicitly set failure status if kernel is going to do anyway.

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

https://bugs.kde.org/show_bug.cgi?id=359871 --- Comment #13 from Ivo Raisr --- Thank you for the fixes. Everything seems to be reasonable, except for the error paths. If an error path is taken (setting status failure), allocated memory is not assigned to ARG6/ARG4. This means

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

https://bugs.kde.org/show_bug.cgi?id=359871 --- Comment #11 from Ivo Raisr --- Thank you for the patch covering Linux. I have only three minor comments: - Why assert ARG7 == 0 in pselect6 wrapper? On some architectures arg7 would be on stack, containing some random values. On

[valgrind] [Bug 345307] Warning about "still reachable" memory when using libstdc++ from gcc 5

https://bugs.kde.org/show_bug.cgi?id=345307 --- Comment #12 from Ivo Raisr --- At the moment we are waiting on libstdc++ changes which need to materialize first. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 345307] Warning about "still reachable" memory when using libstdc++ from gcc 5

https://bugs.kde.org/show_bug.cgi?id=345307 --- Comment #11 from Ivo Raisr --- Yes, it can be done with just one FREERES_DONE hook. But it means we need to pass argument(s) to it (which __freeres functions to call) and this will involve some extra code for all supported

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

https://bugs.kde.org/show_bug.cgi?id=359871 --- Comment #9 from Ivo Raisr --- Steven, would you be able to prepare a patch for Linux using similar technique? I cannot currently devote to developing it for a while. Beware that Linux has ppoll and pselect6 syscalls. And pselect6

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

https://bugs.kde.org/show_bug.cgi?id=359871 Ivo Raisr changed: What|Removed |Added Attachment #97632|0 |1 is obsolete|

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

https://bugs.kde.org/show_bug.cgi?id=359871 --- Comment #7 from Ivo Raisr --- The attached patch has two problems: - it modifies a client memory which may be read-only (see for example bugs for modifying env) - it modifies a client memory and does not restore the changes after

  1   2   >