[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #18617] Better debugging facilities: tracing rule invocation.
From: |
Dave Korn |
Subject: |
[bug #18617] Better debugging facilities: tracing rule invocation. |
Date: |
Wed, 17 Sep 2008 14:26:33 +0000 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.12) Gecko/20050919 Firefox/1.0.7 |
Follow-up Comment #5, bug #18617 (project make):
I would like to draw the attention of everyone in this thread to
http://bashdb.sourceforge.net/remake/
"Remake - GNU Make with comprehensible tracing and a debugger"
I find it an invaluable enhancement to make when debugging complex makefiles
full of generated code. Give it a try: you won't look back once you've
discovered how much easier life is when you can single-step through the source
of a makefile, set breakpoints, inspect variables and see the return values
from called functions.
Stefano:
"It doesn't tell which the implicit rule is", are you sure? The trace shows
> Trying implicit prerequisite `assert.cxx'.
> Found an implicit rule for
>
`/home/stefano/src/reilabs/flash2sip/contrib/src/ptlib_2.2.1/lib/obj_linux_x86_r/assert.o'.
Therefore the implicit rule it is referring to must be of the form
%.o: %.cxx
mustn't it?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?18617>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/