[valgrind] [Bug 381815] Assertion 'newfd >= VG_(fd_hard_limit)' failed

2017-07-14 Thread Kirill A . Korinsky
https://bugs.kde.org/show_bug.cgi?id=381815 Kirill A. Korinsky changed: What|Removed |Added CC||kir...@korins.ky -- You are receiving thi

[valgrind] [Bug 381815] Assertion 'newfd >= VG_(fd_hard_limit)' failed

2017-07-12 Thread Rhys Kidd
https://bugs.kde.org/show_bug.cgi?id=381815 Rhys Kidd changed: What|Removed |Added Version|unspecified |3.14 SVN Status|UNCONFIRMED

[valgrind] [Bug 381815] Assertion 'newfd >= VG_(fd_hard_limit)' failed

2017-07-11 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=381815 --- Comment #9 from Tom Hughes --- Actually that's not the same at all - in fact it's not even a bug (in valgrind) it's just a normal error report about a bug in your program where it is passing uninitialised data to a system call. Please use the users

[valgrind] [Bug 381815] Assertion 'newfd >= VG_(fd_hard_limit)' failed

2017-07-11 Thread Beimbet Daribayev
https://bugs.kde.org/show_bug.cgi?id=381815 --- Comment #8 from Beimbet Daribayev --- I have a same problem. OS: Mac OS 10.12.5. What does this error/warning mean? ==66220== Syscall param msg->desc.port.name points to uninitialised byte(s) ==66220==at 0x1004E834A: mach_msg_trap (in /usr/lib/

[valgrind] [Bug 381815] Assertion 'newfd >= VG_(fd_hard_limit)' failed

2017-07-11 Thread Beimbet Daribayev
https://bugs.kde.org/show_bug.cgi?id=381815 Beimbet Daribayev changed: What|Removed |Added CC||beim...@gmail.com --- Comment #7 from Beimb

[valgrind] [Bug 381815] Assertion 'newfd >= VG_(fd_hard_limit)' failed

2017-07-10 Thread Kirill A . Korinsky
https://bugs.kde.org/show_bug.cgi?id=381815 --- Comment #6 from Kirill A. Korinsky --- Anyway, I just fixed it :) -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 381815] Assertion 'newfd >= VG_(fd_hard_limit)' failed

2017-07-10 Thread Kirill A . Korinsky
https://bugs.kde.org/show_bug.cgi?id=381815 --- Comment #5 from Kirill A. Korinsky --- Created attachment 106527 --> https://bugs.kde.org/attachment.cgi?id=106527&action=edit don't crash on huge limits -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 381815] Assertion 'newfd >= VG_(fd_hard_limit)' failed

2017-07-08 Thread Kirill A . Korinsky
https://bugs.kde.org/show_bug.cgi?id=381815 --- Comment #4 from Kirill A. Korinsky --- Hey, I can't trace valgrind because it calls fcntl over this code: https://gist.github.com/catap/a20b8b1f46b0ba79b9f7297e73df0563 But I can run it in lldb ant provide some output to you. With ulimit -n 1024:

[valgrind] [Bug 381815] Assertion 'newfd >= VG_(fd_hard_limit)' failed

2017-06-30 Thread Kirill A . Korinsky
https://bugs.kde.org/show_bug.cgi?id=381815 --- Comment #3 from Kirill A. Korinsky --- Tom, I have one idea. Can you confirm that fd_hard_limit is getting from getrlimit? If so I think the right way to OS X is using getdtablesize and be sure that F_DUPFD argument less that returned value by getd

[valgrind] [Bug 381815] Assertion 'newfd >= VG_(fd_hard_limit)' failed

2017-06-30 Thread Kirill A . Korinsky
https://bugs.kde.org/show_bug.cgi?id=381815 --- Comment #2 from Kirill A. Korinsky --- Thanks for update. OS X doesn't have strace but it has dtruss that works only from root. and this bug doesn't reproduce from root user. Let me take some time to find a way to get the trace. -- You are recei

[valgrind] [Bug 381815] Assertion 'newfd >= VG_(fd_hard_limit)' failed

2017-06-30 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=381815 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #1 from Tom Hughes --