mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Kaiwan N Billimoria <kaiwan.billimoria@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Chi-Thanh Hoang <chithanh.hoang@gmail.com>
Subject: Re: Issue using faddr2line on kernel modules
Date: Sun, 6 Feb 2022 12:28:59 -0800	[thread overview]
Message-ID: <20220206202859.butmvavyw3tce4hs@treble> (raw)
In-Reply-To: <CAPDLWs_28zYabLjsyT2gq-o6vEzidWB4mpGuUGdiYr0qb6YFWQ@mail.gmail.com>

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?

-- 
Josh


  parent reply	other threads:[~2022-02-06 20:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17  4:57 Kaiwan N Billimoria
2022-01-17 19:48 ` Josh Poimboeuf
2022-01-17 20:27   ` Josh Poimboeuf
2022-01-18  2:40     ` Kaiwan N Billimoria
2022-01-18 17:52       ` Josh Poimboeuf
2022-01-19  3:57         ` Kaiwan N Billimoria
2022-01-19 21:21           ` Josh Poimboeuf
2022-01-19 23:43             ` Josh Poimboeuf
2022-01-20  5:14               ` Kaiwan N Billimoria
2022-01-20 17:17                 ` Josh Poimboeuf
2022-01-20 20:05                   ` Kaiwan N Billimoria
2022-01-27 11:24                     ` Kaiwan N Billimoria
2022-02-06 20:28                     ` Josh Poimboeuf [this message]
2022-02-07  2:23                       ` Kaiwan N Billimoria
2022-02-11  3:31                         ` Kaiwan N Billimoria

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220206202859.butmvavyw3tce4hs@treble \
    --to=jpoimboe@redhat.com \
    --cc=chithanh.hoang@gmail.com \
    --cc=kaiwan.billimoria@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®