Created attachment 143806 [details] modified vfork_hung file that uses fcore instead of gcore. Reproducing steps. 1. gcc -lstdc++ -lpthread -o vfork_hung 1159875526-vfork_hung.cpp 2. ./vfork_hung Works on fc6
Phil, haven't looked at this in a long time, as I recall it creates the core file, just have to ensure that the core file is valid.
Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again.
As mentioned in comment #2 this works. Just verified that the core file produced by fcore seems fine (when loaded into gdb).