Il giorno sab, 18/01/2014 alle 05.42 +0100, Andi Kleen ha scritto: > The dwarf information should be present unless explicitely disabled. > It's either a libunwind or compiler problem. You could file a gcc bug > I suppose. Also check if gdb can backtrace through it. If that works > it's likely unwind. gdb can backtrace perfectly through ls -lR /. Also, recompiling the whole system with -fno-omit-frame-pointer makes perf record & report work like a charm. So I guess it must be the unwinder.
> unwind problems are unfortunately somewhat common (but most seem to > be in handwritten assembler) > > You'll also notice that dwarf unwind profiling is very expensive in overhead. > I usually avoid it because of that. Yes, I did, unfortunately. I'll look into the other issue regarding the compressed kernel modules. Again, thanks for your time. Cheers Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html