[Bug 2100485] Re: Valgrind: FATAL: Private file creation failed.

[Alessandro Astone]

The issue with valgrind specifically seems like a kernel bug to me.

See this python snippet:

python3 -c "import fcntl; fcntl.fcntl(0, fcntl.F_DUPFD, 0x8000000)"

it fails even though 0x8000000 is well below the limit

** Bug watch added: gitlab.gnome.org/chergert/ptyxis/-/issues #379
   https://gitlab.gnome.org/chergert/ptyxis/-/issues/379

** Also affects: ptyxis via
   https://gitlab.gnome.org/chergert/ptyxis/-/issues/379
   Importance: Unknown
       Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to valgrind in Ubuntu.
https://bugs.launchpad.net/bugs/2100485

Title:
  Valgrind: FATAL: Private file creation failed.

Status in Ptyxis:
  Unknown
Status in ptyxis package in Ubuntu:
  New
Status in valgrind package in Ubuntu:
  New

Bug description:
  In plucky:

  $ valgrind apt list
  --4154283:0:libcfile Valgrind: FATAL: Private file creation failed.
     The current file descriptor limit is 1073741804.
     If you are running in Docker please consider
     lowering this limit with the shell built-in limit command.
  --4154283:0:libcfile Exiting now.

  fcntl(3, F_DUPFD, 1073741804)           = -1 ENOMEM (Cannot allocate
  memory)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ptyxis/+bug/2100485/+subscriptions