Re: [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 tra

Re: [racket-dev] Seg fault

There is nothing specific (I guess you mean unsafe functions or FFI). I noticed that most frequently crash happens while background expansion process. > 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 drra

Re: [racket-dev] Seg fault

After some experience with Visual Studio 2010 Express I have a result. Before crash debugger notifies about some unhandled 0xC005 exceptions: Unhandled exception in the "0x65364ac8" in "DrRacket.exe": 0xC005: Access violation when writing "0x049a3fbc" Those exceptions are the same. The c

Re: [racket-dev] Seg fault

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 wrote: > Thanks for th

[racket-dev] Scribble bug?

Hi, Scribble doesn't correctly render scaled bitmaps when the scale produces ratios in the width or height of the pict. The following scribble program: #lang scribble/base @(require pict) @(bitmap "foo.jpg") generates an html file that includes: However, the following scribble program that s

Re: [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

[racket-dev] Seg fault

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