* Linus Torvalds <torva...@linux-foundation.org> wrote:
> On Tue, Jan 28, 2014 at 8:30 AM, H. Peter Anvin <h...@zytor.com> wrote:
> >
> > I don't think there is any way to not break anything... we're
> > introducing a new kind of object ("normalized kernel pointer") here.
>
> I suspect we could just drop the addresses entirely if we have a
> symbolic version. It's not like the hex addresses are all that
> interesting, and in commit messages I actually end up editing them
> out just because they are worthless noise.
Well, I often use the hex numbers to look them up and disassemble them
in a vmlinux via gdb and 'list *0x1234123412341234' - where the
vmlinux has no debuginfo. (Debuginfo takes longer to build so I
generally build without it.)
I'm quite sure other kernel developers do that as well.
> So we could just do "schedule+0x45/0x368" without the actual hex
> address in brackets..
AFAICS this won't work in a symbol-less vmlinux. Is there some trick
to do it with gdb?
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
