Hi Ben, pagein has gone through some considerable re-working since this bug report and I can't reproduce this issue. Do you mind re-trying with the latest version to check if it is now fixed.
Regards, Colin On Tue, 20 Jun 2017 17:34:20 +0200 Ben Wiederhake <benwiederhake.git...@gmx.de> wrote: > Package: pagein > Version: 0.00.03-1 > Severity: important > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > * What led up to the situation? > * What exactly did you do (or not do) that was effective (or > ineffective)? > * What was the outcome of this action? > * What outcome did you expect instead? > > *** End of the template - remove these template lines *** > > Content-Type: text/plain; charset="us-ascii" > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > From: Ben Wiederhake <benwiederhake.git...@gmx.de> > To: Debian Bug Tracking System <sub...@bugs.debian.org> > Subject: pagein: Segfaults roughly every 1 in ten executions > Message-ID: <149796559606.22041.12836038062408551702.reportbug@bewied-eeepc> > X-Mailer: reportbug 7.1.7 > Date: Tue, 20 Jun 2017 15:33:16 +0200 > > Package: pagein > Version: 0.00.03-1 > Severity: normal > > Dear Maintainer, > > How to reproduce: > > user@machine:/$ sudo -s > root@machine:/# pagein -a -v > root@machine:/# pagein -a -v > root@machine:/# pagein -a -v > root@machine:/# pagein -a -v > # You get the idea. > > Expected results: > Runs without issues, as described in the man page > > Actual results: > Sometimes, it crashed without apparent reason. > > Potentially relevant: > - 'pagein -a' also crashes, and more reliably. > - Architecture is i686. > - 1 GiB of physical RAM, and "swap in use" is greater than "mem free" > according to /usr/bin/free > (I know, that just shuffles around the pages; but still, it shouldn't > segfault.) > - Running this on a specific process, e.g. smartd (which runs as root, > and happened to be PID 510 during my tests) also exhibits the bug. > - Running this on a specific "luser" process as non-root also exhibits the > bug. > - Adding a bit of printf debugging reveals which process it's looking at when > it crashes: > Sample from three attempts: smartd (510), policykit (574), reportbug > (22041), exim4 (907) > I don't see any pattern. > - Recompiling from source (apt-get source and 'make' instead of using Debian > tools) > also segfaults. I have the impression that it's more seldom, but that may > be subjective.
