-
Notifications
You must be signed in to change notification settings - Fork 347
2.7.6.3 get crash on my windows7 computer while working with eclipse #1379
Comments
Are you just starting ipy.exe or do you execute any scripts etc? |
"NativeImages" looks like the IronPython assembly might be precompiled using ngen.exe. Is that true? Could you try to disable ngen.exe for IronPython? |
@simplicbe the ipy.exe was invoked by eclipse I think. once I configured the interpreter, a dialog popup repeatedly. |
@markusschaber not pretty sure but I downloaded from https://github.com/IronLanguages/main/releases/tag/ipy-2.7.6.3 |
@markusschaber The installer will NGen the IronPython assemblies during the install. @shiwee Can you provide some additional information on your setup? Are you using PyDev? How do you have it configured? |
Sorry for slow response. I downloaded a 2.7.6.3(IronPython-2.7.6.3.zip), extract and put in drive e, then I go back to Eclipse, right click the ironpython project, choose "properties", then select "PyDev -Interpreter/Grammar" and "Click here to configure an interpreter not listed" to create a new one with the ipy downloaded. then the newly created as the Interpreter. |
I notice you have Grammar version set to 3.0-3.5, can you please try setting it to 2.7 (or similar)? |
I tried this quickly the other day and it crashed for me as well. I didn't get a chance to dig into it though. |
Happening to me too :( debug log from pydev/eclipse
|
I was unable to determine why this was happening back in November. I could look again soon. |
running this command at prompt gave
But it seems to be ok if i start a dummy server on that port (eg nc -l 53089) yields
|
I tried ipy.exe and ipy64.exe as interpreter, both crash, while the previous ironpython(2.7.5) works.
the eclipse version:
Version: Neon Release (4.6.0)
Build id: 20160613-1800
other information:
Faulting application name: ipy.exe, version: 2.7.6.1003, time stamp: 0x57b9a8dd
Faulting module name: clr.dll, version: 4.6.1076.0, time stamp: 0x56d7a0ff
Exception code: 0xc00000fd
Fault offset: 0x00010fee
Faulting process id: 0x17ac
Faulting application start time: 0x01d208dd6658ef8a
Faulting application path: C:\Program Files (x86)\IronPython 2.7\ipy.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: a4d0cc4d-74d0-11e6-9a1a-b8aeed7f0c86
Faulting application name: ipy.exe, version: 2.7.6.1003, time stamp: 0x57b9a8dd
Faulting module name: IronPython.ni.dll, version: 2.7.6.1003, time stamp: 0x57b9a8d9
Exception code: 0xc00000fd
Fault offset: 0x002d0e91
Faulting process id: 0x126c
Faulting application start time: 0x01d208dd6be65f8a
Faulting application path: C:\Program Files (x86)\IronPython 2.7\ipy.exe
Faulting module path: C:\Windows\assembly\NativeImages_v4.0.30319_32\IronPython\5161bc351374575956b910bf5d008f7e\IronPython.ni.dll
Report Id: aa5b7d23-74d0-11e6-9a1a-b8aeed7f0c86
The text was updated successfully, but these errors were encountered: