Re: Segfault in objdump?

2013-06-03 Thread Barret Rhoden
Thanks a lot for the fix! Barret On 2013-06-03 at 13:36 Alan Modra wrote: > Curiousity got the better of me. The problem is triggered by > a) Different memory layout when running objdump -S under make > b) Trailing rubbish at the end of your .stab section > c01f75c8 44001801 e6a013c0

Re: Segfault in objdump?

2013-06-02 Thread Barret Rhoden
> If I run make with your Makefile, it runs for varying amounts of time > before invoking objdump. make -dm shows make re-execing itself many > times. Quite clearly make is touching both olderfile and newerfile > many times. I think you really do have an infinite loop, which for > some unknown r

Re: Segfault in objdump?

2013-06-02 Thread Barret Rhoden
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 inclu

Segfault in objdump?

2013-06-01 Thread Barret Rhoden
Hi - objdump 2.23.1 seems to segfault when called with -S on a large binary, when called from a Makefile that modifies one of its 'include' files. It does not fail on a simple hello-world binary. It does not fail if we do not have -S (-d works). It does not fail if the Makefile doesn't modify