On Thu, Sep 15, 2016 at 09:24:25AM +0200, Peter Zijlstra wrote: > On Wed, Sep 14, 2016 at 10:35:49PM -0700, Stephane Eranian wrote: > > On Wed, Sep 14, 2016 at 7:43 PM, Vince Weaver <vincent.wea...@maine.edu> > > wrote: > > > > > > so the skylake that was fuzzing finally is mostly locked up. > > > > > > Really hard to tell what's going, especially as KASLR made looking up the > > > addresses a big pain. > > > > > I would think there is a way to disable KASLR for this kind of testing! > > I always kill CONFIG_RANDOMIZE_BASE, but there's also talk of killing > the address print entirely.. :-( > > https://lkml.kernel.org/r/20160831165303.tvcudt7wkpechuqt@treble
So you should be able to do something like: echo "list *driver_probe_device+0x223" |gdb vmlinux |grep "is in" Though that's admittedly quite a bit slower than addr2line. -- Josh