Sat 12 Sep 2015 07:34:22 PM UTC, comment #10:
I have reported the crash due to savepath in a separate bug report now, see bug #45947. If this bug is the same as that bug, then it can be investigated and fixed there. Lack of response on this bug means we can't investigate or help debug any further, closing as invalid due to lack of response and specific cause of crash.
|
Fri 07 Aug 2015 12:20:48 PM UTC, comment #9:
I think I can reproduce at least Nicholas' reported crash. If the OP can please confirm that running Octave with --norc makes the crash go away, then I have a reproducible test case.
|
Fri 07 Aug 2015 12:15:48 PM UTC, comment #8:
@Nicholas: thanks for pointing that out. Can you tell us what the contents of your .octaverc looked like after the savepath was done? When I use it, it creates a single long line in the "savepath auto-created section". How long is the line that was added when it caused your Octave to crash on startup? I could see a bug there, may be the same or different from this bug.
Anonymous OP: does the crash still occur if you run octave with the --norc option?
|
Fri 07 Aug 2015 11:51:00 AM UTC, comment #7:
We have the same problem on one of our computers.
When launching the Octave CLI, we got the folloing error:
error: input buffer overflow, can't enlarge buffer because scanner uses REJECT input buffer overflow, can't enlarge buffer because scanner uses REJECT
The problem was resolved(?) by deleting the .octaverc file, and the .config/ folder.
The problem persists (reoccurs on startup) if any folders are added to the path, using the following commands to generate the path:
>> addpath(genpath(pwd))
>> savepath()
The problem (it seems like) was that some svn folders were added, when selecting the very top folder of the project.
By adding the relevant folders manually to the path, the problem has yet to persist.
I don't know if this is any help to you, but this is atleast how we worked around this issue.
/Nicholas
|
Fri 12 Jun 2015 08:58:47 PM UTC, comment #6:
I don't have another Windows machine to install it on. I might be able to beg another machine from someone.
Running Visual Studio debug, I get
Unhandled exception at 0x6feb1f62 in octave-gui.exe: 0xC0000005: Access violation reading location 0x00000007.
I can't get off that to cut and paste.
The first call stack item is
libstdc++6.dll!6feb1f62()
[frames below may be incorrect and/or missing, no symbles loades for libstdc++ (column ends here)
after a break, the next is
No symbols are loaded for any call stack frame. The source code cannot be displayed.
The disassembly shows
6FEB1F59 jne 6FEB1F62
6FEB1F5B jmp 6FEB1F70
6FEB1F5D lea esi,[esi]
6FEB1F60 mov eax,edx
6FEB1F62 mov edx,dword ptr [eax+8]
6FEB1F65 test edx,edx
6FEB1F67 jne 6FEB1F60
6FEB1F69 rep ret
6FEB1F6B nop
it appears that it arrives at 6FEB1Fk62 from a jump if not equal.
I hope that helps
|
Fri 12 Jun 2015 07:56:23 PM UTC, comment #5:
Can you reproduce this problem on a completely different machine? (I'm grasping at straws here.)
|
Fri 12 Jun 2015 03:42:00 PM UTC, comment #4:
The download link has URL
ftp://ftp.gnu.org/gnu/octave/windows/octave-4.0.0_0-installer.exe
I don't remember installing flex. Does it do the parsing for Octave?
It is installed in:
C:\Octave\Octave-4.0.0
Which is my primary drive.
I have re-installed it.
Also, I ran the windows updates and updated the GPU driver, which should have given me the latest version of OpenCL.
|
Fri 12 Jun 2015 03:28:25 PM UTC, comment #3:
Please add The URL wäre you've downloaded The installer.
This is a flex error: http://flex.sourceforge.net/manual/Diagnostics.html
Habe you installed Octave on a network share? In a folder with special Charts? Can you try to reinstall it?
|
Fri 12 Jun 2015 02:50:41 PM UTC, comment #2:
I double clicked on the Octave(GUI) and Octave(CLI) under
All Programs / Octave-4.0.0
After your question, I tried double clicking on the Desktop Icon and the Launch Window (probably CMD window) stays open that I con read it. However, I have to close Windows' popup to copy it. Here is the message:
error: input buffer overflow, can't enlarge buffer because scanner uses REJECT input buffer overflow, can't enlarge buffer because scanner uses REJECT
It also says that Octave was configured for "i686-w64-mingw32".
I installed Octave by double clicking on the file
octave-4.0.0_0-installer.exe
which I downloaded from the Octave site.
|
Fri 12 Jun 2015 02:11:27 PM UTC, comment #1:
With "before opening a window" you mean that as soon as you double-click on the icon, you get a crash?
How did you install Octave?
Are you able to use the GUI-less version of Octave?
|
Fri 12 Jun 2015 01:48:15 PM UTC, original submission:
I installed Octave 4.0 on Windows 7 64-bit with an AMD GPU and CPU. octave-gui.exe crashed before opening a window. The only error message was "octave-gui.exe has stoped working A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."
I tried opening with CLI and it also crashed, but the warning from Windows told me that octave-gui.exe had stopped working. I didn't see a log file to attach.
|