Red Hat Bugzilla – Bug 894770
[abrt] xterm-286-1.fc17: copyLineData: Process /usr/bin/xterm was killed by signal 11 (SIGSEGV)
Last modified: 2013-08-01 01:16:34 EDT
Description of problem:
Trying to run xterm with absurd geometry values. Here's the exact cmdline:
'xterm -bg Wheat -fg Navy -sl 1000 -sb -geometry 8001111x323'
Version-Release number of selected component:
libreport version: 2.0.18
cmdline: xterm -bg Wheat -fg Navy -sl 1000 -sb -geometry 8001111x323
:Thread no. 1 (10 frames)
: #0 copyLineData at ./linedata.c:122
: #1 extractScrnData at ./screen.c:263
: #2 Reallocate at ./screen.c:502
: #3 ScreenResize at ./screen.c:1967
: #4 XtConfigureWidget at Geometry.c:681
: #5 XtResizeWidget at Geometry.c:594
: #6 XawVendorShellExtResize at Vendor.c:445
: #7 XtDispatchEventToWidget at Event.c:882
: #8 _XtDefaultDispatcher at Event.c:1344
: #9 XtDispatchEvent at Event.c:1423
Created attachment 677818 [details]
Created attachment 677819 [details]
Created attachment 677820 [details]
Created attachment 677821 [details]
Created attachment 677822 [details]
Created attachment 677823 [details]
Created attachment 677824 [details]
Created attachment 677825 [details]
Created attachment 677826 [details]
Created attachment 677827 [details]
Created attachment 677828 [details]
Created attachment 677829 [details]
In a quick check, I get
xterm: Error 91, errno 12: Cannot allocate memory
Reason: Alloc: calloc() failed on rows
(I see that the limits are higher on your machine than my VM - perhaps that
allows the geometry to get into some interesting area).
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
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 prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.
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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.