|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #61017] GUI doesn't work anymore, even though CLI works fine |
Date: | Tue, 10 Aug 2021 14:08:01 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.131 Safari/537.36 Edg/92.0.902.67 |
Follow-up Comment #20, bug #61017 (project octave): Hmm... It might help to inspect the point at which Octave is hanging when the GUI doesn't show for you. For this, could you please do the following: - Start Octave with the .bat file like described earlier (`octave.bat --gui`). - With the black Window hanging around, open the Task Manager and switch to the "Details" tab. Look for `octave-gui.exe` in that list and take note of the corresponding PID. - Open the folder where Octave is installed. You should find a file called `cmdshell.bat`. Run that script. That should open an MSYS2 bash. - At that shell, run `gdb -p *PID*` where you replace *PID* with the PID you noted before. - At the (gdb) prompt, execute `thread apply all bt`. That might return a longer list of backtraces that you might need to continue by typing `c`. - Please, paste that output here. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?61017> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |