Follow-up Comment #4, bug #15757 (project make):
Yes, it's OK for global_setlist->next to be non-null in some situations.
This is very helpful, but can you repeat the test and provide the same info
you did in both examples (that is, backtrace, *file, trace the ->next
pointers through to the loop, plus show the value of the global_setlist
variable and its address) and also show the value of
current_variable_set_list and *current_variable_set_list?
Also, if you could print file->name then check your makefiles for that target
and see if there is anything unusual about it (target-specific or
pattern-specific variable settings for it, for example). Also, you might
walk back up the recursion and see what target path (foo depends on bar
depends on baz ...) got you to this point, and look at those targets for any
target-specific variables as well. It would be REALLY great if we could find
a way to reproduce this, even just on Solaris.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=15757>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make
