[SOLVED] running gdb with Makefile

atlantis43 · 02-23-2014, 11:03 PM

Having difficulty using gdb with a "speller" with an Makefile:

Code:

#
# Makefile
#
# Computer Science 50
# Problem Set 5
#


# compiler to use
CC = clang

# flags to pass compiler
CFLAGS = -ggdb -O0 -Qunused-arguments -std=c99 -Wall -Werror
CFLAGS+ = -g
# name for executable
EXE = speller

# space-separated list of header files
HDRS = dictionary.h 

# space-separated list of libraries, if any,
# each of which should be prefixed with -l
LIBS =

# space-separated list of source files
SRCS = speller.c dictionary.c 

# automatically generated list of object files
OBJS = $(SRCS:.c=.o)


# default target
$(EXE): $(OBJS) $(HDRS) Makefile
	$(CC) $(CFLAGS) -o $@ $(OBJS) $(LIBS)

# dependencies 
$(OBJS): $(HDRS) Makefile

# housekeeping
clean:
	rm -f core $(EXE) *.o

The command line for running this program would be:

Quote:

./speller textfile_to_be_spell-checked

Can anyone explain what command line can be used with gdb in order to make use of this app, which would include argv[1]. Can't find any applicable instructions after much searching.
Thanks for your attention.
Thank

NevemTeve · 02-23-2014, 11:29 PM

Code:

gdb ./speller
run textfile_to_be_spell-checked

atlantis43 · 02-24-2014, 07:50 AM

Quote:

Originally Posted by NevemTeve

Code:

gdb ./speller
run textfile_to_be_spell-checked

oh! So simple a solution. Yet so hard to find on the web!
Thanks

NevemTeve · 02-24-2014, 08:26 AM

Note: if you want to run it from Makefile:

Code:

debug: ./speller
        echo 'break main' >debug.tmp
        echo 'run sometestfile' >>debug.tmp
        exec gdb -x debug.tmp ./speller

atlantis43 · 02-25-2014, 10:25 AM

Quote:

Originally Posted by NevemTeve

Note: if you want to run it from Makefile:

Code:

debug: ./speller
        echo 'break main' >debug.tmp
        echo 'run sometestfile' >>debug.tmp
        exec gdb -x debug.tmp ./speller

is there any advantage for "running it" from Makefile?

NevemTeve · 02-25-2014, 11:24 AM

It might be handy if you have to run the debugger again and again with the same parameters (breakpoints, etc)