* About hang in gcov_exit with gnu arm toolchain
@ 2017-06-02 8:15 Reetesh Ranjan
2017-06-02 11:44 ` Nathan Sidwell
0 siblings, 1 reply; 3+ messages in thread
From: Reetesh Ranjan @ 2017-06-02 8:15 UTC (permalink / raw)
To: gcc-patches
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: About hang in gcov_exit with gnu arm toolchain
2017-06-02 8:15 About hang in gcov_exit with gnu arm toolchain Reetesh Ranjan
@ 2017-06-02 11:44 ` Nathan Sidwell
2017-06-03 9:01 ` Reetesh Ranjan
0 siblings, 1 reply; 3+ messages in thread
From: Nathan Sidwell @ 2017-06-02 11:44 UTC (permalink / raw)
To: Reetesh Ranjan, gcc-patches
hi,
> I have opened this bug https://bugs.launchpad.net/gcc-arm-embedded/+bug/1694644 as per the findings I had.
This is Canonical's bug tracker and you seem to be reporting a defect
with their build of gcc. If that is the case, you should be talking
with Canonical.
The gcc bug tracker is https://gcc.gnu.org/bugzilla/.
The diff you provide there seems to be detecting when you've looped 2^32
times, because somethings scrogging the object list to become circular.
That's the actual defect that needs fixing.
nathan
--
Nathan Sidwell
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: About hang in gcov_exit with gnu arm toolchain
2017-06-02 11:44 ` Nathan Sidwell
@ 2017-06-03 9:01 ` Reetesh Ranjan
0 siblings, 0 replies; 3+ messages in thread
From: Reetesh Ranjan @ 2017-06-03 9:01 UTC (permalink / raw)
To: Nathan Sidwell; +Cc: gcc-patches
Hi Nathan,
Please see comments inline.
> On 02-Jun-2017, at 5:14 PM, Nathan Sidwell <nathan@acm.org> wrote:
>
> hi,
>
>> I have opened this bug https://bugs.launchpad.net/gcc-arm-embedded/+bug/1694644 as per the findings I had.
>
> This is Canonical's bug tracker and you seem to be reporting a defect with their build of gcc. If that is the case, you should be talking with Canonical.
As you can see in the bug, they have redirected me to talk to gcc. Please advise on how to proceed.
>
> The gcc bug tracker is https://gcc.gnu.org/bugzilla/.
>
>
> The diff you provide there seems to be detecting when you've looped 2^32 times, because somethings scrogging the object list to become circular. That's the actual defect that needs fixing.
I studied the gcc/ and libgcc/ code. I cannot make out why this is happening, though the debugging session does show this clearly. What I am trying to do with the patch is to show what was required to make things work; however, as you said it is not the fix for the core issue.
About 2^32 times: yes if we had 2^32 files in any given project, it would definitely iterate that many times and fail. In what I saw with my debugging, the circular list contains as many elements as the number of source files in a project, and the loop iterates that many times. There could be a better way to iterate through a circular list, though.
>
> nathan
>
> --
> Nathan Sidwell
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-06-03 9:01 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-06-02 8:15 About hang in gcov_exit with gnu arm toolchain Reetesh Ranjan
2017-06-02 11:44 ` Nathan Sidwell
2017-06-03 9:01 ` Reetesh Ranjan
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).