The code -gen gcc chokes on is a program that uses lots of forward declarations. I am still somewhat clueless as to why the error occurs. I cannot get a minimal example going and finding a bug in a 9000 line file (=size of example the compiler chokes on) is just plain hard.SARG wrote:@AGS
Fbdebugger is compiled without problem (except warnings) with/without the -g option.
By the way, it partially works with the debuggees compiled with the -gen gcc option. But there are still many issues to be resolved. :-(
About your issse, could you test : compile with the -R option (obviously without -g), add a dummy debug line to the c file.
#line 0 "C:\\TEMP\\dev\\testgcc2.bas" just to have at least one data in the debug area
And continue the compilation with the -g option in the gcc.exe command.
Debugging....
I can still see them tmp$ variables pop up left, right and centre in the output. It's going to be hard to get a very good debugging experience with all the renaming/name mangling in the resulting C code. Can't complain too much, though. I'm sure that a couple of releases from now issues can be resolved and the debugging experience is getting better with every release (the code produced by the gcc back end is easier to debug than the code produced by the asm back end when using -gdwarf-2 and not using -fomit-frame-pointer).