C::B features a work-around (probably well hidden):
Goto Settings -> Compiler -> your MinGW compiler -> Tab "Other settings" -> Button "Advanced options" -> In the new window, in tab "Others" enable "Use full path for source files (GDB work-around)"
I saw (C:B is full of settings and subtleties lol) and was just ticked(enabled) by default.
and probably also "Use 8.3 notation". The latter might not work if you have auto-generated files or alike. However it shouldn't be needed for that purpose (I don't recall exactly).
that was unticked by default and as last resource i enable it but the output in C:B's debugger window is ever the same(bad
):
Building to ensure sources are up-to-date
Selecting target:
Debug
Adding source dir: C:\Documents and Settings\Owner\Επιφάνεια εργασίας\BOB\cources\tmp\test\
Adding source dir: C:\Documents and Settings\Owner\Επιφάνεια εργασίας\BOB\cources\tmp\test\
Adding file: C:\Documents and Settings\Owner\Επιφάνεια εργασίας\BOB\cources\tmp\test\bin\Debug\test.exe
Changing directory to: C:/DOCUME~1/Owner/6808~1/BOB/cources/tmp/test/.
Set variable: PATH=.;c:\MinGW\bin;c:\MinGW;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\wbem;C:\Program Files\ATI Technologies\ATI.ACE\Core-Static;c:\MinGW\libexec\gcc\mingw32\4.8.1;C:\Program Files\Geany\bin
Starting debugger: C:\MinGW\bin\gdb.exe -nx -fullname -quiet -args C:/DOCUME~1/Owner/6808~1/BOB/cources/tmp/test/bin/Debug/test.exe
done
Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting breakpoints
Debugger name and version: GNU gdb (GDB) 7.6.1
Child process PID: 2236
[Inferior 1 (process 2236) exited normally]
Debugger finished with status 0
So now what?
PS: i copy/paste the same command we see above in CB's debugger window:
Starting debugger: C:\MinGW\bin\gdb.exe -nx -fullname -quiet -args C:/DOCUME~1/Owner/6808~1/BOB/cources/tmp/test/bin/Debug/test.exe
done
in cmd.com (without any change) and in msys (here only i change "\" to "/" in the first part i.e.the path of gdb) and either worked well
output of msys:
Owner@giannis-b791577 ~
$ C:/MinGW/bin/gdb.exe -nx -fullname -quiet -args C:/DOCUME~1/Owner/6808~1/BO
B/cources/tmp/test/bin/Debug/test.exe
Reading symbols from C:\DOCUME~1\Owner\6808~1\BOB\cources\tmp\test\bin\Debug\tes
t.exe...done.
(gdb) quit
Owner@giannis-b791577 ~
$
So i deduce if C:B use Msys's convention C:B have to change "\" --> "/" in the path of gdb in the command above before start gdb or
wrap the command into " " i.e. "C:\MinGW\bin\gdb.exe" in either case work well.
Lets see
a)
Owner@giannis-b791577 ~
$ C:\MinGW\bin\gdb.exe
sh: C:MinGWbingdb.exe: command not found
not work
b) (see also output of msys above)
Owner@giannis-b791577 ~
$ "C:\MinGW\bin\gdb.exe"
GNU gdb (GDB) 7.6.1
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "mingw32".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
(gdb) quit
Owner@giannis-b791577 ~
$
work as intended
I am wondering how cmd.com can handle flawlessly either combinations (with or without " " and with "/" or "\")
Tnx very much for your reply