Similar crash I've run into
(on my Windows XP Prof 32 bit virtual machine).
Holding the upper right corner of the DrRacket window with left
mouse press I've done some mouse moves to change its size.

Result:

Unhandled exception at 0x68de6fd9 in DrRacket.exe: 0xC0000005: Access violation writing location 0x36163378.

>    libcairo-2.dll!68de6fd9()
[Frames below may be incorrect and/or missing, no symbols loaded for libcairo-2.dll]
     libcairo-2.dll!68e292e9()
     msvcrt.dll!77c2c2de()
     libcairo-2.dll!68e1b34e()
     libcairo-2.dll!68e1e6d3()
     libcairo-2.dll!68e20533()
     libcairo-2.dll!68de1d25()
     libcairo-2.dll!68dfbfbc()
     libcairo-2.dll!68dfb446()
     libcairo-2.dll!68df59ef()
     libpixman-1-0.dll!6537529e()
     libcairo-2.dll!68dd8785()
     libcairo-2.dll!68dd8b24()
     libracket3m_9xtiki.dll!1006ac24()
     libcairo-2.dll!68e1fcc6()
     libcairo-2.dll!68e24fa4()
     msvcrt.dll!77c2c3c9()
     msvcrt.dll!77c2c3c9()
     msvcrt.dll!77c2c3c9()
     libcairo-2.dll!68e0553e()
     libcairo-2.dll!68dd89c0()
     libcairo-2.dll!68e47941()
     libcairo-2.dll!68e1fcc6()
     libcairo-2.dll!68ddde52()
     libracket3m_9xtiki.dll!1006ac24()
     libcairo-2.dll!68dd345b()
     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!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!7e418734()
     user32.dll!7e418816()
     user32.dll!7e428ea0()
     user32.dll!7e428eec()
     ntdll.dll!7c90e453()
     user32.dll!7e4194be()
     user32.dll!7e428e0d()
     libracket3m_9xtiki.dll!1006ac24()
     libracket3m_9xtiki.dll!1026562d()
     libracket3m_9xtiki.dll!100015af()
     libracket3m_9xtiki.dll!10012561()
     libracket3m_9xtiki.dll!10014146()
     libracket3m_9xtiki.dll!1006ac24()
     libracket3m_9xtiki.dll!1000dcae()
     libracket3m_9xtiki.dll!10001625()
     libracket3m_9xtiki.dll!10265886()
     libracket3m_9xtiki.dll!100015af()
     libracket3m_9xtiki.dll!10012561()
     libracket3m_9xtiki.dll!10014146()
     libracket3m_9xtiki.dll!1006ac24()
     libracket3m_9xtiki.dll!1000dcae()
     libracket3m_9xtiki.dll!10001625()
     libracket3m_9xtiki.dll!10265886()
     user32.dll!7e418734()
     user32.dll!7e418816()
     user32.dll!7e4189cd()
     user32.dll!7e418a10()
     libracket3m_9xtiki.dll!1026562d()
     libracket3m_9xtiki.dll!100015af()
     libracket3m_9xtiki.dll!10012561()
     libracket3m_9xtiki.dll!10014146()
     libracket3m_9xtiki.dll!10014372()
     libracket3m_9xtiki.dll!100611c8()
     libracket3m_9xtiki.dll!1006120f()
     libracket3m_9xtiki.dll!1006120f()
     libracket3m_9xtiki.dll!1006ac24()
     libracket3m_9xtiki.dll!100964b0()
     libracket3m_9xtiki.dll!100966fd()
     libracket3m_9xtiki.dll!100a0b2a()
     libracket3m_9xtiki.dll!100611c8()
     libracket3m_9xtiki.dll!1006120f()
     libracket3m_9xtiki.dll!100611c8()
     libracket3m_9xtiki.dll!1006ac24()
     libracket3m_9xtiki.dll!1008dd77()
     libracket3m_9xtiki.dll!1008deeb()
     libracket3m_9xtiki.dll!1006ac24()
     libracket3m_9xtiki.dll!1006d4cb()
     libracket3m_9xtiki.dll!1006ac24()
     libracket3m_9xtiki.dll!1008e0c6()
     libracket3m_9xtiki.dll!1009b2f7()
     libracket3m_9xtiki.dll!1009f8be()
     libracket3m_9xtiki.dll!10024d76()
     DrRacket.exe!00406ba7()
     DrRacket.exe!00409e2f()
     kernel32.dll!7c817067()


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

Reply via email to