[Octave-bug-tracker] [bug #64735] `pkg load io` crashes Octave GUI with no error

[Markus Mützel]

Follow-up Comment #5, bug #64735 (project octave):

It doesn't look like a permissions issue of the Temp folder. But who knows?

Given the value of OCTAVE_HOME, it looks like the partition that Octave is
installed on uses a file system that doesn't support short file names.
Arun's suggestion of installing in a folder without any spaces in its path
might help to work-around this issue. 

But I agree that Octave shouldn't crash like it does for you.

To find out why it is crashing (and potentially fix that), it would be nice to
get a backtrace from the crash.

Could you please do the following?
* Open Octave and execute `getpid`. Take note of the PID that is displayed.
* Go to the Windows start menu, find Octave's group in "All Apps", and open
"Bash Shell" from there. A window with a shell should appear.
* At that prompt, execute `gdb -p <PID>` (where you replace `<PID>` with the
PID that you queried in the first step). If this attaches correctly to the
Octave process, its window will feel like it is "frozen".
* At the (gdb) prompt, execute `c`. After that, the Octave window should
"unfreeze". But the (gdb) prompt will look like it's "frozen" now.
* Execute the commands that make Octave crash for you.
* At that point, the (gdb) prompt should be reactive again. Enter `thread
apply all bt` and show the output that you get. (That might be multiple
screens. Make sure to grab the entire output.)





    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64735>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/