On 2013-06-02 at 14:23 Alan Modra wrote: > On Sat, Jun 01, 2013 at 10:21:16AM -0700, Barret Rhoden wrote: > > It does not fail if the Makefile doesn't > > modify a file that it includes. > > Doesn't this mean you have a make loop?
AFAIK, make reads in the included file once, then attempts to update it as a goal, sees it needs updated, and reincludes it since it knows it has changed. At that point, it is up to date, and doesn't re-touch it. http://www.gnu.org/software/make/manual/make.html#Remaking-Makefiles > I doubt that this objdump segfault is worth pursuing. I can just avoid calling it with -S. I was just wondering if anyone would recognize the problem easily. Thanks for reading. =) For those curious, the segfault is in _bfd_stab_section_find_nearest_line(). Barret ------------- Program received signal SIGSEGV, Segmentation fault. 0x00002ac48acbabdf in _bfd_stab_section_find_nearest_line () from /usr/lib64/binutils/x86_64-pc-linux-gnu/2.23.1/libbfd-2.23.1.so (gdb) bt #0 0x00002ac48acbabdf in _bfd_stab_section_find_nearest_line () from /usr/lib64/binutils/x86_64-pc-linux-gnu/2.23.1/libbfd-2.23.1.so #1 0x00002ac48acdf60b in _bfd_elf_find_nearest_line_discriminator () from /usr/lib64/binutils/x86_64-pc-linux-gnu/2.23.1/libbfd-2.23.1.so #2 0x0000000000408d85 in show_line () #3 0x00000000004097ad in disassemble_section () #4 0x00002ac48acba0ec in bfd_map_over_sections () from /usr/lib64/binutils/x86_64-pc-linux-gnu/2.23.1/libbfd-2.23.1.so #5 0x0000000000405ff4 in disassemble_data () #6 0x000000000040827e in dump_bfd () #7 0x000000000040aaa0 in display_any_bfd () #8 0x000000000040ab60 in display_file.part.7 () #9 0x0000000000405159 in main () _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
