-
rdubner authored
Discovered that although gcc is putting the .debug_gdb_scripts into foo.sym.o, the loader is somehow stripping it out when the executable foo is created. Consequently, I have changed cobcd to place foo-gdb.py next to the foo executable. Will investigate to see if a nicer solution is possible. Also found that the SFIX logic that puts a .loc directive at every function's entry point was looking for the text "@function" in Intel and Arm assembler. The SPARC assembly code has "#function" at the equivalent point. Also need to handle problems caused by SPARC being a big-endian machine. This is the first I've seen that.
0f38edd5