Re: [racket-users] Futures + threads SIGSEGV

Hi Sam, On 02. 05. 20 14:26, Sam Tobin-Hochstadt wrote: > I successfully reproduced this on the first try, which is good. Here's > my debugging advice (I'm also looking at it): > > 1. To use a binary with debugging symbols, use > `racket/src/build/racket/racket3m` from the checkout of the Racket

Re: [racket-users] Futures + threads SIGSEGV

I opened https://github.com/racket/racket/issues/3145 to avoid too much mailing list traffic, and posted a stack trace there. Sam On Sat, May 2, 2020 at 8:31 AM Matthew Flatt wrote: > > I wasn't able to produce a crash on my first try, but the Nth try > worked, so this is very helpful! > > I'm

Re: [racket-users] Futures + threads SIGSEGV

Hi Dominik, Ah that explains why I was getting an incorrect number of threads! I didn’t think about using future-visualizer, but I’ll give it a try. Thanks! Dex > On May 2, 2020, at 2:27 PM, Dominik Pantůček > wrote: > > Hi Dex, > >> On 02. 05. 20 14:10, Dexter Lagan wrote: >> Hello, >>

Re: [racket-users] Futures + threads SIGSEGV

I wasn't able to produce a crash on my first try, but the Nth try worked, so this is very helpful! I'm investigating, too... At Sat, 2 May 2020 08:26:10 -0400, Sam Tobin-Hochstadt wrote: > I successfully reproduced this on the first try, which is good. Here's > my debugging advice (I'm also

Re: [racket-users] Futures + threads SIGSEGV

Hi Dex, On 02. 05. 20 14:10, Dexter Lagan wrote: > Hello, > >   I’ve been getting inconsistent results as well. A while ago I made a > benchmark based on a parallel spectral norm computation. The benchmark > works fine on Windows on most systems and uses all cores, but crashes > randomly on

Re: [racket-users] Futures + threads SIGSEGV

I successfully reproduced this on the first try, which is good. Here's my debugging advice (I'm also looking at it): 1. To use a binary with debugging symbols, use `racket/src/build/racket/racket3m` from the checkout of the Racket repository that you built. 2. When running racket in GDB, there

Re: [racket-users] Futures + threads SIGSEGV

Hello, I’ve been getting inconsistent results as well. A while ago I made a benchmark based on a parallel spectral norm computation. The benchmark works fine on Windows on most systems and uses all cores, but crashes randomly on other systems. I haven’t been able to figure out why. On Linux

[racket-users] Futures + threads SIGSEGV

Hello fellow Racketeers, during my research into how Racket can be used as generic software rendering platform, I've hit some limits of Racket's (native) thread handling. Once I started getting SIGSEGVs, I strongly suspected I am doing too much unsafe operations - and to be honest, that was true.