[racket-dev] Seg fault

Try to play with indicator on the picture:
http://s27.postimg.org/vt4pk0y6b/Image_222.png

When background expansion is turned on the indicator is green.
Right click on it and turn background expansion off.
Then it becomes red.
Right click again and turn background expansion on.
Then it becomes transparent or invisible (bug?).

I just played this way on one of my Windows XP virtual machines and
DrRacket crashed. Fortunately I have VS debugger there:

Unhandled exception at 0x65375981 in DrRacket.exe: 0xC0000005: Access
violation reading location 0x2d3510bc.

>	libpixman-1-0.dll!65375981()
 	[Frames below may be incorrect and/or missing, no symbols loaded for
libpixman-1-0.dll]
 	libpixman-1-0.dll!653027a0()
 	libcairo-2.dll!68e1c3a6()
 	libcairo-2.dll!68e1c86e()
 	libcairo-2.dll!68e1c94e()
 	libcairo-2.dll!68dd7912()
 	libcairo-2.dll!68dd8850()
 	libcairo-2.dll!68e2021b()
 	libcairo-2.dll!68e03689()
 	msvcrt.dll!77c2c3c9()
 	libcairo-2.dll!68dffec8()
 	libcairo-2.dll!68e0180b()
 	libracket3m_9xtiki.dll!10001266()
 	libcairo-2.dll!68dd3333()
 	libracket3m_9xtiki.dll!10265609()
 	libracket3m_9xtiki.dll!1026562d()
 	libracket3m_9xtiki.dll!100015af()
 	libracket3m_9xtiki.dll!10012561()
 	libracket3m_9xtiki.dll!10014146()
 	libracket3m_9xtiki.dll!10014372()
 	libracket3m_9xtiki.dll!10091e2a()
 	libracket3m_9xtiki.dll!1009caba()
 	libracket3m_9xtiki.dll!1006ad19()
 	libracket3m_9xtiki.dll!1006d4cb()
 	libracket3m_9xtiki.dll!1006d4cb()
 	libracket3m_9xtiki.dll!1006d4cb()
 	libracket3m_9xtiki.dll!1006ac24()
 	libracket3m_9xtiki.dll!1006d42b()
 	libracket3m_9xtiki.dll!1006ac24()
 	libracket3m_9xtiki.dll!1006ac24()
 	libracket3m_9xtiki.dll!1000dcae()
 	libracket3m_9xtiki.dll!10001625()
 	libracket3m_9xtiki.dll!10265886()
 	user32.dll!7e418734()
 	user32.dll!7e418816()
 	user32.dll!7e428ea0()
 	user32.dll!7e428eec()
 	ntdll.dll!7c90e453()
 	user32.dll!7e4194d2()
 	user32.dll!7e428f10()
 	user32.dll!7e4278e0()
 	ntdll.dll!7c90e453()
 	user32.dll!7e4193e9()
 	user32.dll!7e4193a8()
 	libracket3m_9xtiki.dll!1006ac24()
 	libracket3m_9xtiki.dll!1000dcae()
 	libracket3m_9xtiki.dll!1006ac24()
 	libracket3m_9xtiki.dll!100964b0()
 	libracket3m_9xtiki.dll!100966fd()
 	libracket3m_9xtiki.dll!100a0b2a()
 	libracket3m_9xtiki.dll!100610ea()
 	libracket3m_9xtiki.dll!1006d471()
 	libracket3m_9xtiki.dll!1006d42b()
 	libracket3m_9xtiki.dll!1006ac24()
 	libracket3m_9xtiki.dll!100964b0()
 	libracket3m_9xtiki.dll!100966fd()
 	libracket3m_9xtiki.dll!100a0b2a()
 	libracket3m_9xtiki.dll!1006ac24()
 	libracket3m_9xtiki.dll!100611c8()
 	libracket3m_9xtiki.dll!1006120f()
 	libracket3m_9xtiki.dll!1006ac24()
 	libracket3m_9xtiki.dll!100964b0()
 	libracket3m_9xtiki.dll!100966fd()
 	libracket3m_9xtiki.dll!100a0b2a()
 	libracket3m_9xtiki.dll!1009f8be()
 	libracket3m_9xtiki.dll!10024d76()
 	DrRacket.exe!00406ba7()
 	DrRacket.exe!00409e2f()
 	kernel32.dll!7c817067()



> I also tried both the 64 and 32 bit builds on my windows vm and
> couldn't get it to crash.
>
> Is there something specific you're doing in drracket? I just opened a
> few files and clicked around and nothing untoward happened.
>
> Robby
>
> On Thu, Jul 31, 2014 at 9:42 AM, Matthew Flatt <mflatt at cs.utah.edu> wrote:
>> 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
>> _________________________
>>   Racket Developers list:
>>   http://lists.racket-lang.org/dev
>