[racket-dev] Seg fault
Thanks for the report. Unfortunately, I'm not able to replicate the
crash, so I'm not sure what to recommend.
If you have Visual Studio installed, then it may offer to open a
debugger, or you could attach to the process while a "program has
crashed" dialog is showing. A C-level backtrace extracted from the
debugger might be helpful.
If you don't have Visual Studio installed, does the OS offer any
additional information at all?
At Thu, 31 Jul 2014 16:54:15 +0700 (NOVT), "Evgeny Odegov" wrote:
> Today some conditions met on my machine and DrRacket began to crash almost
> immediately after run. So I reproduced it many times.
>
> The results of last several crashes:
>
> * Seg fault (internal error) at 31a3a4c
> Seg fault (internal error) at 31a3a4c
> Seg fault (internal error) at 31a3a4c
>
> * Seg fault (internal error) at 25863a4c
> Seg fault (internal error) at 25863a4c
> Seg fault (internal error) at 25863a4c
>
> * Seg fault (internal error) at 29e93a4c
> Seg fault (internal error) at 29e93a4c
> Seg fault (internal error) at 29e93a4c
>
> * Seg fault (internal error) at 4223a4c
> Seg fault (internal error) at 4223a4c
> Seg fault (internal error) at 4223a4c
>
> * Seg fault (internal error) at 1c55392ac
> Seg fault (internal error) at 1c55392ac
> Seg fault (internal error) at 1c55392ac
>
> * Seg fault (internal error) at 256b41fc
> Seg fault (internal error) at 256b41fc
> Seg fault (internal error) at 256b41fc
>
> Racket version: (32 bit x86) 6.1.0.2--2014-07-14(c7dd72a/a)
> OS: Windows 7 Prof 64 bit
>
> I also decided to try current snapshot 6.1.0.3--2014-07-30(f3a8883/a).
> The crashes are repeated:
>
> * Seg fault (internal error) at 2b9c3a4c
> Seg fault (internal error) at 2b9c3a4c
> Seg fault (internal error) at 2b9c3a4c
>
> * Seg fault (internal error) at 28b53a4c
> Seg fault (internal error) at 28b53a4c
> Seg fault (internal error) at 28b53a4c
>
> _________________________
> Racket Developers list:
> http://lists.racket-lang.org/dev