FAQ
For some reason it's not visible here:

---------- Forwarded message ----------
From: Russ Cox <rsc@golang.org>
Date: Fri, Nov 30, 2012 at 12:43 AM
Subject: Re: [golang-dev] code review 6851125: runtime: better stack
traces in race reports (issue 6851125)
To: Dmitry Vyukov <dvyukov@google.com>, golang-dev
<golang-dev@googlegroups.com>, "reply@codereview-hr.appspotmail.com"
<reply@codereview-hr.appspotmail.com>

LGTM

https://codereview.appspot.com/6851125/

Search Discussions

  • Dvyukov at Nov 30, 2012 at 6:29 am
    *** Submitted as
    https://code.google.com/p/go/source/detail?r=73fcac092bd1 ***

    runtime: better stack traces in race reports
    When a race happens inside of runtime (chan, slice, etc),
    currently reports contain only user file:line.
    If the line contains a complex expression,
    it's difficult to figure out where the race exactly.
    This change adds one more top frame with exact
    runtime function (e.g. runtime.chansend, runtime.mapaccess).

    R=golang-dev
    CC=golang-dev
    https://codereview.appspot.com/6851125


    https://codereview.appspot.com/6851125/

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupgolang-dev @
categoriesgo
postedNov 30, '12 at 6:28a
activeNov 30, '12 at 6:29a
posts2
users1
websitegolang.org

1 user in discussion

Dvyukov: 2 posts

People

Translate

site design / logo © 2022 Grokbase