[valgrind] [Bug 196335] valgrind: m_libcfile.c:73 (vgPlain_safe_fd): Assertion 'newfd >= VG_(fd_hard_limit)' failed.

2023-02-21 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=196335

--- Comment #11 from Paul Floyd  ---
(not to mention that a bug that was for Darwin 9.7 is probably not the same
thing as Linux Docker).

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 196335] valgrind: m_libcfile.c:73 (vgPlain_safe_fd): Assertion 'newfd >= VG_(fd_hard_limit)' failed.

2023-02-21 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=196335

Paul Floyd  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REOPENED|RESOLVED
 CC||pjfl...@wanadoo.fr

--- Comment #10 from Paul Floyd  ---
Closing this as a duplicate of 465435. See the analysis there.

IMO this is a Docker bug. It lies when it tells us what the file descriptor
rlimit is. Then when we try to move one of our internal fds out of the way at
the top of this range the fcntl dupfd fails.

*** This bug has been marked as a duplicate of bug 465435 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 196335] valgrind: m_libcfile.c:73 (vgPlain_safe_fd): Assertion 'newfd >= VG_(fd_hard_limit)' failed.

2023-02-21 Thread Thorsten Glaser
https://bugs.kde.org/show_bug.cgi?id=196335

Thorsten Glaser  changed:

   What|Removed |Added

 CC||t.gla...@tarent.de
 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED
 Resolution|WAITINGFORINFO  |---

--- Comment #9 from Thorsten Glaser  ---
A colleage could reproduce this bug today:

I have no name!@9019b147885f:/code$ valgrind --track-origins=yes pytest  

valgrind: m_libcfile.c:66 (vgPlain_safe_fd): Assertion 'newfd >=
VG_(fd_hard_limit)' failed.
Segmentation fault (core dumped)

This is a Debian bookworm Docker image under Arch Linux; even “valgrind false”
fails like this.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 196335] valgrind: m_libcfile.c:73 (vgPlain_safe_fd): Assertion 'newfd >= VG_(fd_hard_limit)' failed.

2019-06-16 Thread Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=196335

Tom Hughes  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |WAITINGFORINFO

--- Comment #8 from Tom Hughes  ---
Please don't apply KDE policies to non-KDE packages.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 196335] valgrind: m_libcfile.c:73 (vgPlain_safe_fd): Assertion 'newfd >= VG_(fd_hard_limit)' failed.

2019-06-16 Thread fbampaloukas
https://bugs.kde.org/show_bug.cgi?id=196335

fbampaloukas  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

--- Comment #7 from fbampaloukas  ---
Closing as Worksforme due to inactivity for more than 15 days as per:

https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging#Policies

Fanis

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 196335] valgrind: m_libcfile.c:73 (vgPlain_safe_fd): Assertion 'newfd >= VG_(fd_hard_limit)' failed.

2019-06-16 Thread fbampaloukas
https://bugs.kde.org/show_bug.cgi?id=196335

fbampaloukas  changed:

   What|Removed |Added

 Resolution|NOT A BUG   |WORKSFORME
 CC||marinus.savorit...@tuta.io

--- Comment #6 from fbampaloukas  ---
Closing as Worksforme due to inactivity for more than 15 days as per:

https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging#Policies

Fanis

-- 
You are receiving this mail because:
You are watching all bug changes.