On Sat, Sep 17, 2016 at 11:11:44AM +0200, Vegard Nossum wrote:
> On 16 September 2016 at 21:17, Josh Poimboeuf wrote:
> > On Fri, Sep 16, 2016 at 11:12:10AM -0700, Linus Torvalds wrote:
> >> Side note: I find addr2line almost completely useless in many cases
> >> not because of address space rando
On 16 September 2016 at 21:17, Josh Poimboeuf wrote:
> On Fri, Sep 16, 2016 at 11:12:10AM -0700, Linus Torvalds wrote:
>> Side note: I find addr2line almost completely useless in many cases
>> not because of address space randomization, but because of how complex
>> the inlining often is. I just h
On Fri, Sep 16, 2016 at 12:17 PM, Josh Poimboeuf wrote:
>
> I think that issue is solved by addr2line's '--inline' option, which the
> script uses:
Oh, well, even better. I clearly don't know addr2line well enough, and
having a script that does this correctly automatically is clearly what
*I* nee
On Fri, Sep 16, 2016 at 11:12:10AM -0700, Linus Torvalds wrote:
> On Fri, Sep 16, 2016 at 7:48 AM, Josh Poimboeuf wrote:
> >
> > Here's something a lot faster than gdb, which also handles duplicate
> > symbols properly.
>
> Ack.
>
> Side note: I find addr2line almost completely useless in many c
On Fri, Sep 16, 2016 at 7:48 AM, Josh Poimboeuf wrote:
>
> Here's something a lot faster than gdb, which also handles duplicate
> symbols properly.
Ack.
Side note: I find addr2line almost completely useless in many cases
not because of address space randomization, but because of how complex
the
dt7wkpechuqt@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.
Here's something a lot faster than gdb, which a
6 matches
Mail list logo
