On Sat, 28 Jul 2012, Ronald S. Bultje wrote: > On Fri, Jul 27, 2012 at 1:01 PM, Loren Merritt <[email protected]> > wrote: > >> %%.b_idx_loop: >> Automatically generates a different label for each instantiation of the >> macro. > > My disassembly now looks like this: > > 0x00000001004c43b4 <ff_h264_loop_filter_strength_mmx2.nofield+25>: jne > 0x1004c44d1 <ff_h264_loop_filter_strength_mmx2.bidir> > 0x00000001004c43ba <ff_h264_loop_filter_strength_mmx2.nofield+31>: xor > %r8d,%r8d > 0x00000001004c43bd <[email protected]_idx_loop+0>: pxor %mm0,%mm0 > 0x00000001004c43c0 <[email protected]_idx_loop+3>: test %r11d,%r8d > > Can I somehow keep the function name in it? I find that somewhat > useful when debugging.
Nope. And I've patched my objdump to remove function names prefixed to local labels. The bigger problem is that gdb doesn't know the difference between local labels and functions, so disassembly will fail to encompass a whole function if it contains any labels, regardless of what they're named. For this reason, I sometimes find it easier to `strip -x` before using gdb. --Loren Merritt _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
