From: Yao Qi <qiyaoltc@gmail.com>
To: deffo@gmx.de
Cc: GDB <gdb@sourceware.org>
Subject: Re: GDB does not stop at assembly code address
Date: Tue, 18 Oct 2016 19:19:00 -0000 [thread overview]
Message-ID: <CAH=s-PO51tuy7hawLzkN0f5oL29dc-+mkEoD-oCer=x_HcQqRw@mail.gmail.com> (raw)
In-Reply-To: <trinity-afbcff27-0734-44e2-b2db-cbf9a57aa90b-1476809585225@3capp-gmx-bs05>
On Tue, Oct 18, 2016 at 12:53 PM, <deffo@gmx.de> wrote:
> Here's the output:
>
> (gdb) b startup_32
> Breakpoint 1 at 0xc1000000: file arch/x86/kernel/head_32.S, line 97.
> (gdb) print startup_32
> $1 = {<text variable, no debug info>} 0xc1000000 <startup_32>
> (gdb) info breakpoints
> Num Type Disp Enb Address What
> 1 breakpoint keep y 0xc1000000 arch/x86/kernel/head_32.S:97
>
> (gdb) b start_kernel
> Breakpoint 1 at 0xc1be3755: file init/main.c, line 480.
> (gdb) print start_kernel
> $1 = {void (void)} 0xc1be3755 <start_kernel>
> (gdb) info breakpoints
> Num Type Disp Enb Address What
> 1 breakpoint keep y 0xc1be3755 in start_kernel at init/main.c:480
>
Looks breakpoint is set on the right place. Nothing wrong there.
> I guess the "no debug info" would be the explanation, but why is that? The address is listed as a FUNC in readelf -Ws vmlinux, thus it should be correct. What do I have to do?
>
"no debug info" is about startup_32, which is written in assembly without debug
information. It is nothing wrong there. I have no idea why breakpoint on
startup_32 is not hit.
--
Yao (齐尧)
next prev parent reply other threads:[~2016-10-18 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 16:53 deffo
2016-10-18 19:19 ` Yao Qi [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-14 15:21 deffo
2016-10-17 11:46 ` Yao Qi
2016-10-18 19:47 ` Jan Kratochvil
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='CAH=s-PO51tuy7hawLzkN0f5oL29dc-+mkEoD-oCer=x_HcQqRw@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=deffo@gmx.de \
--cc=gdb@sourceware.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