[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPDLWs88HXMW_yPH4zC=XFz6p6aTJs55BoZCXYYPSmDwRBbdRg@mail.gmail.com>
Date: Mon, 7 Feb 2022 07:53:32 +0530
From: Kaiwan N Billimoria <kaiwan.billimoria@...il.com>
To: Josh Poimboeuf <jpoimboe@...hat.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Chi-Thanh Hoang <chithanh.hoang@...il.com>
Subject: Re: Issue using faddr2line on kernel modules
On Mon, Feb 7, 2022 at 1:59 AM Josh Poimboeuf <jpoimboe@...hat.com> wrote:
>
> On Fri, Jan 21, 2022 at 01:35:13AM +0530, Kaiwan N Billimoria wrote:
> > > Try this one?
> >
> > Definitely better !
> > This is the o/p i now get:
> >
> > $ <...>linux-5.10.60/scripts/faddr2line ./oops_tryv2.ko
> > do_the_work.cold+0x68/0x126
> > do_the_work.cold+0x68/0x126:
> > delay_sec at <...>/oops_tryv2/../../convenient.h:279
> > $
> >
> > The source file+line-no doesn't show up here though... (as it's a foo.cold()?).
> > (I'm unsure why the line delay_sec at <...>convenient.h:279 shows up
> > ; i don't call this delay_sec() func directly... anyway, that's my
> > problem.)
>
> Hm... do you get the same result with addr2line?
addr2line works correctly.
And, so does the patched faddr2line, when i tried it out now on
another VM! Lemme check some more and get back, thanks.
- Kaiwan.
>
>
> --
> Josh
>
Powered by blists - more mailing lists