Messages in this thread | | | Date | Tue, 28 Jan 2014 18:52:20 +0100 | From | Richard Weinberger <> | Subject | Re: [GIT PULL] x86/kaslr for v3.14 |
| |
Am 28.01.2014 18:35, schrieb Linus Torvalds: > On Tue, Jan 28, 2014 at 9:24 AM, Richard Weinberger <richard@nod.at> wrote: >> >> Hmm, my gdb does not like that notion. >> >> (gdb) list schedule+0x45 >> Function "schedule+0x45" not defined. > > I don't have a debug build, so maybe it's something specific to gdb > actually seeing type information and then being confused.. > > Can you do "x/10i schedule+0x45" because that definitely works for me. > But I literally detest DBUG_INFO builds, because it's useless crap. > 99% of everything I debug is from people reporting problems on their > kernels, so it's not like my local debug info would match that anyway.
x/10i schedule+0x45 works.
> Anyway, if it's a type information thing due to DEBUG_INFO that > confuses gdb and makes it think that the "+0x45" part doesn't make > sense, you may need to add a cast to get gdb to ignore the type > information. IOW, does > > list (void *)schedule + 0x45 > > work for you?
Nope.
(gdb) list (void *)schedule + 0x45 Function "(void *)schedule + 0x45" not defined.
> I happen to have gdb-7.6.50 here that I tested with, but I've used > "symbol+offset" forever afaik, so it's definitely not something new.
I'm on 7.5.1.
Thanks, //richard
| |