public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Reetesh Ranjan <reeteshranjan@piaxis.tech>
To: gcc-patches@gcc.gnu.org
Subject: About hang in gcov_exit with gnu arm toolchain
Date: Fri, 02 Jun 2017 08:15:00 -0000	[thread overview]
Message-ID: <3C59484E-355F-48B9-A025-8D53520791EF@piaxis.tech> (raw)

Hi,

I have opened this bug https://bugs.launchpad.net/gcc-arm-embedded/+bug/1694644 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 bug mentioned here has all the description, and how I managed to debug and solve 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 need some more guidance, especially on testing this out, as well as a review of the problem. I would appreciate if you can help me out based on the description in the above mentioned bug.

Thanks,
Reetesh

             reply	other threads:[~2017-06-02  8:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02  8:15 Reetesh Ranjan [this message]
2017-06-02 11:44 ` Nathan Sidwell
2017-06-03  9:01   ` Reetesh Ranjan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C59484E-355F-48B9-A025-8D53520791EF@piaxis.tech \
    --to=reeteshranjan@piaxis.tech \
    --cc=gcc-patches@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).