Red Hat Bugzilla – Bug 1028196
[abrt] cpulimit-1.1-3.fc19: ____strtol_l_internal: Process /usr/bin/cpulimit was killed by signal 11 (SIGSEGV)
Last modified: 2015-02-12 05:55:37 EST
Description of problem:
cpulimit --limit 30 -p $GPID -z
7380 Segmentation fault (core dumped) cpulimit --limit 30 -p $GPID -z
[7219:7290:1107/162536:ERROR:download.cc(99)] PostClientToServerMessage() failed during GetUpdates
[97:117:1107/162536:ERROR:platform_thread_linux.cc(99)] Failed to set nice value of thread to -10
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[118:262:1107/162702:ERROR:platform_thread_linux.cc(99)] Failed to set nice value of thread to -10
Version-Release number of selected component:
cmdline: cpulimit --limit 30 -p -z
runlevel: N 5
Thread no. 1 (3 frames)
#0 ____strtol_l_internal at ../stdlib/strtol_l.c:300
#1 strtol at ../stdlib/strtol.c:109
#2 atoi at /usr/include/stdlib.h:280
Created attachment 821314 [details]
Created attachment 821315 [details]
Created attachment 821316 [details]
Created attachment 821317 [details]
Created attachment 821318 [details]
Created attachment 821319 [details]
Created attachment 821320 [details]
Created attachment 821321 [details]
Created attachment 821322 [details]
Created attachment 821323 [details]
Created attachment 821324 [details]
Should be fixed by latest build (rebuild against the github sources).
For Fedora 20 it is already in latest build, for Fedora 19 still needs karma.
Could please check if that fixes it for you too?
Christos, yes, it looks like it's caging the process properly and no more segmentation faults. Thank you!
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
As this issue is resolved, I'm closing the bug report.