From: matwey.kornilov@gmail.com (Matwey V. Kornilov)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to correctly decode fun+X/Y
Date: Thu, 3 Dec 2015 21:14:38 +0300 [thread overview]
Message-ID: <n3q0qe$gdc$1@ger.gmane.org> (raw)
Hello,
I have the following stack trace:
[ 1351.381696] a.out S c0afb050 0 1676 1658 0x00000000
[ 1351.387048] [<c0afb050>] (__schedule) from [<c0afb4d0>]
(schedule+0x58/0xcc)
[ 1351.392436] [<c0afb4d0>] (schedule) from [<c069369c>]
(tty_port_block_til_ready+0x1a8/0x35c)
[ 1351.396937] [<c069369c>] (tty_port_block_til_ready) from [<c06ab220>]
(uart_open+0x118/0x158)
[ 1351.402560] [<c06ab220>] (uart_open) from [<c068b768>]
(tty_open+0x11c/0x600)
[ 1351.407043] [<c068b768>] (tty_open) from [<c03e1ce4>]
(chrdev_open+0xb4/0x188)
[ 1351.412556] [<c03e1ce4>] (chrdev_open) from [<c03db3dc>]
(do_dentry_open+0x230/0x330)
[ 1351.417038] [<c03db3dc>] (do_dentry_open) from [<c03dc64c>]
(vfs_open+0x64/0x6c)
[ 1351.422470] [<c03dc64c>] (vfs_open) from [<c03eaf5c>]
(do_last+0x510/0xd94)
[ 1351.426909] [<c03eaf5c>] (do_last) from [<c03eb86c>]
(path_openat+0x8c/0x270)
[ 1351.432398] [<c03eb86c>] (path_openat) from [<c03ecd78>]
(do_filp_open+0x70/0xd4)
[ 1351.436815] [<c03ecd78>] (do_filp_open) from [<c03dc9cc>]
(do_sys_open+0x120/0x1e4)
[ 1351.442117] [<c03dc9cc>] (do_sys_open) from [<c03dcab8>]
(SyS_open+0x28/0x30)
[ 1351.447046] [<c03dcab8>] (SyS_open) from [<c021cd40>]
(ret_fast_syscall+0x0/0x34)
Could please explain, how to correctly decode
tty_port_block_til_ready+0x1a8/0x35c to the instruction or line of code
using gdb?
I have kernel image and separate debug info.
next reply other threads:[~2015-12-03 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 18:14 Matwey V. Kornilov [this message]
2015-12-03 18:34 ` How to correctly decode fun+X/Y Dave Tian
2015-12-03 18:43 ` Nicholas Mc Guire
2015-12-04 9:12 ` Daniel Baluta
2015-12-07 8:53 ` Andrey Skvortsov
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='n3q0qe$gdc$1@ger.gmane.org' \
--to=matwey.kornilov@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.