🚀 go-pugleaf

Consider the 4 files below:

(first one is empty)
a.h:

foo.c:
	main()
	{
	}

b.c:
	#include "a.h"
	blahe()
	{
	}
c.c:
	#include "a.h"
	ick()
	{
	}

Compile with:

cc -g -o f foo.c b.c c.c

./gdb ./f
GDB is free software and you are welcome to distribute copies of it
 under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.6, Copyright 1992 Free Software Foundation, Inc...

Undefined command: "include".  Try "help".

Reading symbols from ./f...done.

Setting up the environment for debugging gdb.
Function "fatal" not defined.
(gdb) break main
Reading in symbols for foo.c... and b.c...
stEnd with storage class 1 not handled...done.
Breakpoint 1 at 0x400190: file foo.c, line 4.
(gdb)

The symbols for the source file b.c are read in because apparent gdb
thinks foo.c depends on information in b.c.

Cleary this is ludicrous.  It is interesting to note that if you
transpose b.c and c.c on the compile line then c.c fill be read in after
foo.c (instead of b.c as shown above.)


-Rob Ryan