Bug#879674: /bin/ps:ps/display.c:66: please report this bug

2019-12-17 Thread Craig Small
Hmm, that's an interesting situation you have there with /proc under a process. It looks like it is getting the /proc/stat and the /proc//stat confused and crashing. I'll have a look at the code around reading the stat file in and see if it can be a bit more robust. Unfortunately, the older

Bug#879674: /bin/ps:ps/display.c:66: please report this bug

2019-11-17 Thread Marco d'Itri
On Oct 24, Craig Small wrote: > Are you sure it's just a lack of memory causing this problem? > It's going to be a bit tricky to fix with just a crash message. I have seen a similar bug being triggered on a compromised customer server. strace: ... stat("/proc/22299", {st_mode=S_IFDIR|0555,

Bug#879674: /bin/ps:ps/display.c:66: please report this bug

2017-11-04 Thread zoli
Hi, Ehem... While writing this, I realized that ps is not even piped to mawk... Here is the code I was running with more detail: MAIN SCRIPT:#!/bin/bash ... /bin/bash -c -- " source SCRIPT_LIB monitor_pid || exit -1; " 2>&1 \ |

Bug#879674: /bin/ps:ps/display.c:66: please report this bug

2017-10-24 Thread Craig Small
Hi, Are you sure it's just a lack of memory causing this problem? It's going to be a bit tricky to fix with just a crash message. - Craig > > -- Craig Small https://dropbear.xyz/ csmall at : enc.com.au Debian GNU/Linuxhttps://www.debian.org/ csmall at : debian.org

Bug#879674: /bin/ps:ps/display.c:66: please report this bug

2017-10-24 Thread zoltan
Package: procps Version: 2:3.3.12-3 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I was running a script for some days, and over time, firefox memory usage cranked up, I suspect this has led