libreport version: 2.0.7 abrt_version: 2.0.6 backtrace_rating: 4 cmdline: gdb --interpreter mi2 --nx comment: My program sometimes crashes without any rational reason, then in debugging, when a vector (from STL) is going to be declared, GDB crashed!:((((( crash_function: vgetargskeywords executable: /usr/bin/gdb kernel: 3.1.2-1.fc16.x86_64 pid: 3881 pwd: /home/masood/workspace/CAP reason: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV) reported_to: file: pidgin1 time: Tue 06 Dec 2011 07:44:12 PM IRST uid: 1000 username: masood backtrace: Text file, 1300005 bytes dso_list: Text file, 3210 bytes environ: Text file, 2303 bytes event_log: Text file, 6903 bytes maps: Text file, 13826 bytes pidgin1: Text file, 2981 bytes smolt_data: Text file, 3302 bytes build_ids: :16053224897d5961128b8819407b87a74957908a :84b11ab3a043dc234c53c6c83d9a8aa37af97695 :bfa713fda01e5880fdba7387f6053e350dcf9738 :3ed9e61c2b7e707ce244816335776afa2ad0307d :aa733447f84020c94a66814e501a36e248cbb43d :2c5957a6a123fe37bde0be6e87957f0a02f2b865 :9e8739a57b5d15d950b3daacdfb2383ae7faf7d6 :7f61fb1b16866dcb14575dfc5dda295a8c416071 :6ae19b07608683ea0d76f1406c6d50d5a2793ecc :ab59942678bcdecb23756804dcd0aac63ccc1669 :086b8d05a2fb6992634d2e22e69d7aefe16cf390 :4ea09f2cc6fa21696beac3f95cdd4160cfddd35f :9d1209fc79304f03cc839de1c0036c61b48dfff8 :638db099ff5fb986d1a092629d1bb1dca5be4904 :022f1a6511ab7f46cc5b6f0df5852b50dfd46c85 :15c25336f081a938b4c7bdc13478f620c614242d :b682f0c21c6ed2e0d474de137d5499999d451235 :7109859fdd4912a7b36eea239079fd72b5575d18 :0f0c9eed63ed279ceb0aef109eff8bcbb351e4bb :e00197fd41716ba040c25b4210f1a3a0eab95133 :104e675cb52acd6a43ff3a77bada7825efd595fa :b9746e6e639b060dcd2809a4c46655ee77838bf1 :48aea888319e1848137073c9cbde54a4c2a731c9 :6502dd4813f98137c70e6e05cc43828f5c2263c1 :9c23cc77b5763600b189289e892983ebb6c172c8 :b0eabf9093defbfdd0857ea3ed1a4563b743434e :b2addb78b534f66e1c4fb01a407861181151bd8a :e2e67b3ae2579e1667b73ad385f61552931024e9 :66b8a549e5dfccb29eee911c9a1f987d05f12613 :cd77f398c344fb85d62bb939fa1896091055f835 :e567a4b498aa9dfc484575e666a17925f0944318 :4cd8fa570a1bbc72cf724584eff76012b2f80b57 :9c4040663276f2d45ef7e52080f2580bc4eeae42 :71ddb5b548bc9a76c3095b7c2a5f4906c85a79d8 :3cbc639da8b05f5cd87202ff77c5c335313d3276 :48d3cff26c916dff6cbcb5e67d5cf6d391f6ccca :0949b493f01e0553822be3bd14def9dbe79b804f var_log_messages: :Dec 6 14:02:01 Masood-Laptop kernel: [ 3109.119879] [ 2471] 1000 2471 51315 2342 1 0 0 gdb :Dec 6 14:26:58 Masood-Laptop kernel: [ 4606.633399] [ 2471] 1000 2471 51315 1264 0 0 0 gdb :Dec 6 15:02:46 Masood-Laptop kernel: [ 6753.611860] [ 2471] 1000 2471 51315 9 0 0 0 gdb :Dec 6 19:44:12 Masood-Laptop kernel: [ 5373.510874] gdb[3881]: segfault at 7fffe2b8ee28 ip 00000036c30ee49f sp 00007fffe2b8ee00 error 6 in libpython2.7.so.1.0[36c3000000+171000] :Dec 6 19:44:14 Masood-Laptop abrt[3901]: Saved core dump of pid 3881 (/usr/bin/gdb) to /var/spool/abrt/ccpp-2011-12-06-19:44:12-3881 (96407552 bytes)
Created attachment 541473 [details] File: environ
Created attachment 541474 [details] File: event_log
Created attachment 541475 [details] File: backtrace
Created attachment 541476 [details] File: pidgin1
Created attachment 541477 [details] File: smolt_data
Created attachment 541478 [details] File: maps
Created attachment 541479 [details] File: dso_list
Phil, have you an idea if pretty printer could loop infinitely?
Yes, for sure. If the std::vector is corrupted or not allocated on the heap there is no telling where the addresses within the std::vector point to, and it could loop continuously into the weeds. Eventually it would sigsegv. Without a testcase or description of events , though, I cannot say definitively if this is the case in this bug report
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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
AFAIK not fixed yet.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.