Similar to issue #2685 and #2019, but with a different behavior.

Environment information

• Operating System: Windows 10 21H2 and Ubuntu 18 Virtual Machine
• Cutter version: 2.3.2-HEAD-1d07ebc
• Obtained from:
  • Built from source
  • Downloaded release from Cutter website or GitHub
  • Distribution repository
• File format:
  Tested on PE32 and ELF executables.

Describe the bug
Admittedly poor practice on my behalf including white space in file paths, but:

The initial opening and debugging of the executable works as expected. After the debugger terminates the disassembly view is populated by 'Invalid' instructions and an error is provided in the console that the executable cannot be opened. From the output it appears that spaces are being parsed as a subdirectory, such that E:/ExamplePath/Execute Me/test.exe becomes E:/ExamplePath/Execute/ Me/test.exe

To Reproduce

Steps to reproduce the behavior:

1. Create a directory whose path contains a space, and place an executable inside of the directory
2. Open the executable in Cutter
3. Launch a native debugging session, and terminate the session (either by program completion or manually)
4. See error: In console 'ERROR: Cannot open file' appears, and file is unloaded from Cutter

Expected behavior
Cutter retains the directory of the original executable and correctly loads the executable after a debugging session.

Additional context
Problem seems to occur both in linux and windows.
The issue disappears if the the file path's spaces are removed.