This bug was fixed in the package psmisc - 22.21-2.1ubuntu0.1
---
psmisc (22.21-2.1ubuntu0.1) xenial; urgency=medium
* d/p/fix-pstree-seg-fault.patch: Fix pstree segfault (LP: #1837444)
-- Lucas Kanashiro Mon, 12 Aug 2019
17:44:51 -0300
** Changed in: psmisc (Ubuntu Xenial)
** Changed in: psmisc (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837444
Title:
pstree seg fault
To manage notifications about this bug go to:
htt
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837444
Title:
pstree seg fault
To manage noti
I tried this out on one of out systems affected and it definitely
resolves the bug. Before:
:~$ for ((i=0;i<20;i++)); do pstree -alp 2>&1 > /dev/null; done
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
:~$
After:
:~$
Hello Russell, or anyone else affected,
Accepted psmisc into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/psmisc/22.21-2.1ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
** Changed in: psmisc (Ubuntu Xenial)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837444
Title:
pstree seg fault
To manage notific
** Merge proposal linked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/psmisc/+git/psmisc/+merge/371266
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837444
Title:
pstree seg fault
** Description changed:
- Impact
- --
+ [Impact]
Users might face a segmentation fault crash while executing 'pstree'.
Backporting this fix will avoid 'pstree' breakage in our users' systems under
certain circumstances.
This is a timing issue where if the 'get_threadname' functio
** Also affects: psmisc (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: psmisc (Ubuntu)
Status: Triaged => Fix Released
** Changed in: psmisc (Ubuntu Xenial)
Status: New => Triaged
** Changed in: psmisc (Ubuntu Xenial)
Importance: Undecided => Low
--
** Description changed:
+ Impact
+ --
+
+ Users might face a segmentation fault crash while executing 'pstree'.
Backporting this fix will avoid 'pstree' breakage in our users' systems under
+ certain circumstances.
+
+ This is a timing issue where if the 'get_threadname' function is called
Unfortunately no. I have a system where it reproduces readily and others
where it does not, but am unsure of what the difference between the
systems is. Only obvious thing is that the bad system has 7000+
processes
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
https://sourceforge.net/p/psmisc/patches/33/ patch forwarded upstream,
with upstream confirmation
link to upstream commit that included this fix, among other changes:
https://sourceforge.net/p/psmisc/code/ci/265fa43ee48898001130b90d3656d48af5d241aa/
--
You received this bug notification because
Thanks for filing this bug in Ubuntu.
This looks like a straight forward patch, already applied upstream. If I
understand it correctly, it might be hard to reproduce, because the
thread deletion has to happen at the right time. Do you encounter this
frequently, or have a way to reproduce that does
13 matches
Mail list logo
