From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 38622 invoked by alias); 2 Jun 2017 08:15:47 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 36343 invoked by uid 89); 2 Jun 2017 08:15:37 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.5 required=5.0 tests=BAYES_05,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=guidance, H*MI:tech, findings X-HELO: sender-of-o52.zoho.com Received: from sender-of-o52.zoho.com (HELO sender-of-o52.zoho.com) (135.84.80.217) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 02 Jun 2017 08:15:36 +0000 Received: from [192.168.0.101] (180.151.117.139 [180.151.117.139]) by mx.zohomail.com with SMTPS id 1496391332708388.80221371303037; Fri, 2 Jun 2017 01:15:32 -0700 (PDT) From: Reetesh Ranjan Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: About hang in gcov_exit with gnu arm toolchain Message-Id: <3C59484E-355F-48B9-A025-8D53520791EF@piaxis.tech> Date: Fri, 02 Jun 2017 08:15:00 -0000 To: gcc-patches@gcc.gnu.org X-ZohoMailClient: External X-SW-Source: 2017-06/txt/msg00097.txt.bz2 Hi, I have opened this bug https://bugs.launchpad.net/gcc-arm-embedded/+bug/169= 4644 as per the findings I had. I noticed inexplicable hang in gcov_exit/__= gcov_flush while trying to do code coverage for an embedded project. The bu= g mentioned here has all the description, and how I managed to debug and so= lve it, and a patch. The gnu arm toolchain maintainers have directed me to = talk on this gcc email. I have gone through the gcc contribution guidelines; however, I think I nee= d some more guidance, especially on testing this out, as well as a review o= f the problem. I would appreciate if you can help me out based on the descr= iption in the above mentioned bug. Thanks, Reetesh