Thread: GCC Debugging and Makefile issues

Ok, I've tried running gcc with -g a number of ways but GDB always says "no debugging symbols found." I'm using MinGW/MSYS with GCC 4.7.2 on Win7.

My makefle is definitely messy, but the only thing I ever really had to go on was the crap Dev-C++ created when I was using that early on. Do I need something more than -g? Or does this copy of GCC just not compile debugging symbols? There are no compile errors and the program works, but I can't get it to add debugging symbols for GDB for anything. Every time I break something I have to debug the hard way.

Code:

# Project: RenegadeEx

NAME  = rex.exe

CC = gcc
WINDRES = windres
RES  = rex.res
OBJ  = $(OBJPATH)rex.o $(OBJPATH)tab_hook.o $(OBJPATH)tab_results.o $(OBJPATH)tab_search.o $(OBJPATH)tab_settings.o $(OBJPATH)lib_api.o $(OBJPATH)lib_fileio.o $(OBJPATH)lib_listview.o $(OBJPATH)lib_misc.o $(OBJPATH)lib_rex.o $(OBJPATH)lib_search.o $(OBJPATH)lib_memory.o $(OBJPATH)$(RES)
LDFLAGS = -s -mwindows -lwsock32 -lcomctl32 -lpsapi
CFLAGS = -O2 -s
OBJPATH = obj/
GLOBALINCLUDES = _types.h rex.h lib_fileio.h lib_misc.h lib_search.h


.PHONY: all

all: $(NAME)


clean:
	rm -f $(OBJ)

Debug: $(NAME)

cleanDebug: clean

$(NAME): $(OBJ)
	$(CC) $(OBJ) -o $(NAME) $(LDFLAGS)

$(OBJPATH)rex.res: rex.rc rex_gui.h
	$(WINDRES) -i rex.rc -J rc -o $(OBJPATH)rex.res -O coff

$(OBJPATH)rex.o: rex.c rex_gui.h $(GLOBALINCLUDES)
	$(CC) -c rex.c -o $(OBJPATH)rex.o $(CFLAGS)

#Tabs

$(OBJPATH)tab_hook.o: tab_hook.c rex_gui.h $(GLOBALINCLUDES)
	$(CC) -c tab_hook.c -o $(OBJPATH)tab_hook.o $(CFLAGS)

$(OBJPATH)tab_results.o: tab_results.c rex_gui.h $(GLOBALINCLUDES)
	$(CC) -c tab_results.c -o $(OBJPATH)tab_results.o $(CFLAGS)

$(OBJPATH)tab_search.o: tab_search.c rex_gui.h $(GLOBALINCLUDES)
	$(CC) -c tab_search.c -o $(OBJPATH)tab_search.o $(CFLAGS)

$(OBJPATH)tab_settings.o: tab_settings.c rex_gui.h $(GLOBALINCLUDES)
	$(CC) -c tab_settings.c -o $(OBJPATH)tab_settings.o $(CFLAGS)

#Libraries

$(OBJPATH)lib_api.o: lib_api.c $(GLOBALINCLUDES)
	$(CC) -c lib_api.c -o $(OBJPATH)lib_api.o $(CFLAGS)

$(OBJPATH)lib_fileio.o: lib_fileio.c lib_fileio.h _types.h
	$(CC) -c lib_fileio.c -o $(OBJPATH)lib_fileio.o $(CFLAGS)

$(OBJPATH)lib_listview.o: lib_listview.c $(GLOBALINCLUDES)
	$(CC) -c lib_listview.c -o $(OBJPATH)lib_listview.o $(CFLAGS)

$(OBJPATH)lib_memory.o: lib_memory.c $(GLOBALINCLUDES)
	$(CC) -c lib_memory.c -o $(OBJPATH)lib_memory.o $(CFLAGS)

$(OBJPATH)lib_misc.o: lib_misc.c lib_misc.h _types.h
	$(CC) -c lib_misc.c -o $(OBJPATH)lib_misc.o $(CFLAGS)

$(OBJPATH)lib_rex.o: lib_rex.c $(GLOBALINCLUDES)
	$(CC) -c lib_rex.c -o $(OBJPATH)lib_rex.o $(CFLAGS)

$(OBJPATH)lib_search.o: lib_search.c lib_search.h _types.h
	$(CC) -c lib_search.c -o $(OBJPATH)lib_search.o $(CFLAGS)

Hah. Ok, that solves the debugging issue. Thanks. It'd be nice if I knew the right way to set that file up. I can't even figure out what half those arguments are "-O2" ??? "-O coff" ???

You may want to read the documentation for gcc. Here is a list of most of the options for the compiler. Option Summary The -O2 is one of the optimization switches.

Jim

Thanks. I'm also curious if stripping debug info with -s matters? I mean, if it's an open source project anyway, I don't care about leaving debug symbols in the release. I'm just wondering if it affects performance at all.