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: 0xC005: Access
violation writing
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
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
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
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
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
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
No, the errors are printed in a terminal window. Since I have visual studio
loaded on that machine, I get a VS pop up asking if I want to enter the
debugger. I can see the stack in the debugger, but there are no symbols,
etc so I'm not sure a stack trace there would be helpful. If I don't enter
the
Do you get a button that lets you get a stacktrace?
Robby
On Sat, Apr 21, 2012 at 7:54 PM, Doug Williams
wrote:
> I downloaded Saturday's build and get the same Seg Fault (the address is
> different) when I run my large app under DrRacket. However, the application
> runs fine while I compile it
I downloaded Saturday's build and get the same Seg Fault (the address is
different) when I run my large app under DrRacket. However, the application
runs fine while I compile it and run it standalone.
On Thu, Apr 19, 2012 at 9:32 AM, Williams, Doug wrote:
> I have downloaded the latest pre-releas
I have downloaded the latest pre-release for v5.3
(plt-5.2.901.1-bin-i386-win32.exe). All of my PLaneT collections load
and run fine. But, my large application at work fails to run - it dies
during startup with "Seg Fault (internal error during gc) at 58720044"
printed (twice) in a new window. It's
11 matches
Mail list logo
