Bug 568252 - [abrt] crash in mcpp-2.7.2-4.fc12: Process /usr/bin/mcpp was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in mcpp-2.7.2-4.fc12: Process /usr/bin/mcpp was killed by signal...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mcpp
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kiyoshi Matsui
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d9236f3960b5adda461b832cb9c...
: 591772 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-25 06:50 UTC by ramana
Modified: 2010-12-03 22:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-03 22:22:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.79 KB, text/plain)
2010-02-25 06:50 UTC, ramana
no flags Details

Description ramana 2010-02-25 06:50:25 UTC
abrt 1.0.7 detected a crash.

architecture: i686
cmdline: /usr/bin/mcpp -DHOST=hd-ramanacharyv.virtusa.com -DSERVERHOST=hd-ramanacharyv.virtusa.com -DSRVR_hd_ramanacharyv_virtusa_com -DDISPLAY_NUM=0 -DCLIENTHOST=hd-ramanacharyv.virtusa.com -DCLNT_hd_ramanacharyv_virtusa_com -DVERSION=11 -DREVISION=0 '-DVENDOR=Fedora -DVENDO' -DVNDR_Fedora_Project -DRELEASE=10705000 -DNUM_SCREENS=1 -DEXT_SGI_GLX -DEXT_GLX -DEXT_DAMAGE -DEXT_Composite -DEXT_XINERAMA -DEXT_RANDR -DEXT_RENDER -DEXT_XFIXES -DEXT_XC_MISC -DEXT_XKEYBOARD -DEXT_SYNC -DEXT_BIG_REQUESTS -DEXT_XTEST -DEXT_XInputExtension -DEXT_MIT_SHM -DEXT_SHAPE -DEXT_Generic_Event_Extension -DEXT_DRI2 -DEXT_DOUBLE_BUFFER -DEXT_X_Resource -DEXT_XVideo -DEXT_DPMS -DEXT_XFree86_DGA -DEXT_XFree86_VidModeExtension -DEXT_MIT_SCREEN_SAVER -DSCREEN_NUM=0 -DWIDTH=1280 -DHEIGHT=1024 -DX_RESOLUTION=3787 -DY_RESOLUTION=3793 -DPLANES=24 -DBITS_PER_RGB=8 -DCLASS=TrueColor -DCLASS_TrueColor=33 -DCOLOR -DCLASS_TrueColor_24=33 -DCLASS_DirectColor_24=34 -DCLASS_TrueColor_32=100 /tmp/kde-VIRTUSAramanacharyv/kcminittQ2117.tmp
component: mcpp
executable: /usr/bin/mcpp
kernel: 2.6.31.12-174.2.22.fc12.i686.PAE
package: mcpp-2.7.2-4.fc12
rating: 4
reason: Process /usr/bin/mcpp was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

backtrace
-----
warning: section .gnu.liblist not found in /var/cache/abrt-di/usr/lib/debug/.build-id/70/552a39180d6c686baf1ed1f984d4548a64f982.debug
warning: section .gnu.conflict not found in /var/cache/abrt-di/usr/lib/debug/.build-id/70/552a39180d6c686baf1ed1f984d4548a64f982.debug
warning: section .gnu.liblist not found in /var/cache/abrt-di/usr/lib/debug/.build-id/70/552a39180d6c686baf1ed1f984d4548a64f982.debug
warning: section .gnu.conflict not found in /var/cache/abrt-di/usr/lib/debug/.build-id/70/552a39180d6c686baf1ed1f984d4548a64f982.debug
warning: section .gnu.liblist not found in /var/cache/abrt-di/usr/lib/debug/.build-id/70/552a39180d6c686baf1ed1f984d4548a64f982.debug
warning: section .gnu.conflict not found in /var/cache/abrt-di/usr/lib/debug/.build-id/70/552a39180d6c686baf1ed1f984d4548a64f982.debug
Core was generated by `/usr/bin/mcpp -DHOST=hd-ramanacharyv.virtusa.com -DSERVERHOST=hd-ramanacharyv.v'.
Program terminated with signal 11, Segmentation fault.
#0  _IO_new_fclose (fp=0x0) at iofclose.c:52
52	iofclose.c: No such file or directory.
	in iofclose.c

Thread 1 (Thread 2140):
#0  _IO_new_fclose (fp=0x0) at iofclose.c:52
        status = <value optimized out>
#1  0x00c08951 in mcpp_lib_main (argc=<value optimized out>, 
    argv=<value optimized out>) at main.c:441
        in_file = 0xbf9248c1 "/tmp/kde-VIRTUSAramanacharyv/kcminittQ2117.tmp"
        out_file = 0x0
#2  0x080484bc in main (argc=<value optimized out>, 
    argv=<value optimized out>) at main_libmcpp.c:8
No locals.
From        To          Syms Read   Shared Object Library
0x00c083f0  0x00c21688  Yes (*)     /usr/lib/libmcpp.so.0
0x00aa6990  0x00bb24e0  Yes (*)     /lib/libc.so.6
0x00a6e830  0x00a85ccf  Yes (*)     /lib/ld-linux.so.2
(*): Shared library is missing debugging information.
$1 = 0x0
No symbol "__glib_assert_msg" in current context.

Comment 1 ramana 2010-02-25 06:50:29 UTC
Created attachment 396233 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 08:51:54 UTC
*** Bug 591772 has been marked as a duplicate of this bug. ***

Comment 3 Bug Zapper 2010-11-03 21:22:09 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2010-12-03 22:22:36 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.


Note You need to log in before you can comment on or make changes to this bug.