Yeah, source code and dumping memory seems to be the only and right way to know
exactly why.
Thanks for your responses
YUU
> On Mar 9, 2020, at 11:39 PM, Leszek Kubik wrote:
>
> To understand (make a best guess) a race condition case you need to dump the
> physical memory and analyze it
On Mon, Mar 9, 2020 at 4:16 PM Yuu LongXue wrote:
>
> Hi all,
>
> Slice is not thread safe for write operation if without lock, this is true
> and I know this feature. but recently, I got a panic which caused by writing
> a slice concurrently with out lock occasionally and I can't figure out
On Mon, Mar 9, 2020 at 9:16 AM Yuu LongXue wrote:
>
> Hi all,
>
> Slice is not thread safe for write operation if without lock, this is true
> and I know this feature. but recently, I got a panic which caused by writing
> a slice concurrently with out lock occasionally and I can't figure out
Hi all,
Slice is not thread safe for write operation if without lock, this is true and
I know this feature. but recently, I got a panic which caused by writing a
slice concurrently with out lock occasionally and I can't figure out why.
### the process as below:
1. define a slice: var x
