From: nilesh.tayade@netscout.com (nilesh)
To: kernelnewbies@lists.kernelnewbies.org
Subject: functions about dump backtrace function names in mips arch
Date: Tue, 04 Jan 2011 12:14:56 +0530 [thread overview]
Message-ID: <1294123496.6697.3.camel@nilesh-desktop> (raw)
In-Reply-To: <AANLkTi=B+bKGDDXxAXT3OEC0jD0GskxkB6Vq2x_z7xqd@mail.gmail.com>
On Mon, 2011-01-03 at 22:32 +0800, loody wrote:
> hi all:
>
> 2011/1/3 Sowmya Sridharan <sowmya.sridharan@tcs.com>:
> >
> > Hi,
> >
> > I was able to check it in 2.6.36 version of kernel, and it is defined in
> > traps.c.
> > http://lxr.linux.no/linux+v2.6.36/arch/mips/kernel/traps.c#L205
> >
> > dump_stack() calls show_backtrace function which had been show_trace in the
> > earlier kernel versions.
[...]
> >
> >
[...]
> > Regards,
> > Sowmya
> thanks for your kind help, that is what I want.
> previously, I only see the address instead of function name, but after
> I select CONFIG_KALLSYMS as Y, I can see the function names also.
> BTW, what is the mechanism that kernel take to find out the function name?
Enabling the config option, it allows to build the symbol table for
kernel. It uses /proc/kallsyms.
Below links could help:
http://tldp.org/HOWTO/Module-HOWTO/x627.html
http://fixunix.com/kernel/134739-proc-kallsyms-symbol-size.html
> Regards,
> miloody
--
Thanks,
Nilesh
prev parent reply other threads:[~2011-01-04 6:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTims5ejcB8hmH5nE3zR5R_57oF88x=NS438ZOM3V@mail.gmail.com>
2011-01-02 8:26 ` functions about dump backtrace function names in mips arch loody
2011-01-02 8:27 ` loody
2011-01-02 11:01 ` Mulyadi Santosa
2011-01-03 7:43 ` Sowmya Sridharan
2011-01-03 14:32 ` loody
2011-01-03 14:39 ` loody
2011-01-04 6:44 ` nilesh [this message]
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=1294123496.6697.3.camel@nilesh-desktop \
--to=nilesh.tayade@netscout.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).