Re: [go-nuts] Sample code with races needed for presentation

[Haddock]

Thanks, Ian. There is plenty of stuff there ;-).

Am Donnerstag, 9. März 2017 00:20:33 UTC+1 schrieb Ian Lance Taylor:
>
> On Wed, Mar 8, 2017 at 2:51 PM, Haddock  
> wrote: 
> > 
> > I'm working on a comparison between concurency in Go and on the JVM. For 
> > that reason I would like to show some Go code that has problem with 
> > incorrect synchronization and will cause race conditions or deadlocks. 
> Ich 
> > want to demonstrate how they are partially caught at compile time or at 
> > runtime using the runtime analysis tool for that. This would be an 
> > eye-opener, because that does not exist on the JVM (except for some very 
> > expensive runtime analysis tools). 
> > 
> > I can write a small Go programm, but I'm not that proficient in Go to 
> > construct that kind of sample code myself in reasonable time. So that's 
> why 
> > I wrote this post. 
>
> You may want to look at the collection of tests in 
> runtime/race/testdata.  Those are programs that will cause the race 
> detector to report errors if run with -race. 
>
> Ian 
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] Sample code with races needed for presentation

[Ian Lance Taylor]

On Wed, Mar 8, 2017 at 2:51 PM, Haddock  wrote:
>
> I'm working on a comparison between concurency in Go and on the JVM. For
> that reason I would like to show some Go code that has problem with
> incorrect synchronization and will cause race conditions or deadlocks. Ich
> want to demonstrate how they are partially caught at compile time or at
> runtime using the runtime analysis tool for that. This would be an
> eye-opener, because that does not exist on the JVM (except for some very
> expensive runtime analysis tools).
>
> I can write a small Go programm, but I'm not that proficient in Go to
> construct that kind of sample code myself in reasonable time. So that's why
> I wrote this post.

You may want to look at the collection of tests in
runtime/race/testdata.  Those are programs that will cause the race
detector to report errors if run with -race.

Ian

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[go-nuts] Sample code with races needed for presentation

[Haddock]

Hello,

I'm working on a comparison between concurency in Go and on the JVM. For 
that reason I would like to show some Go code that has problem with 
incorrect synchronization and will cause race conditions or deadlocks. Ich 
want to demonstrate how they are partially caught at compile time or at 
runtime using the runtime analysis tool for that. This would be an 
eye-opener, because that does not exist on the JVM (except for some very 
expensive runtime analysis tools).  

I can write a small Go programm, but I'm not that proficient in Go to 
construct that kind of sample code myself in reasonable time. So that's why 
I wrote this post.

Thanks in advance, Haddock

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.