From: deffo@gmx.de
To: gdb@sourceware.org
Subject: GDB does not stop at assembly code address
Date: Fri, 14 Oct 2016 15:21:00 -0000 [thread overview]
Message-ID: <trinity-155e70d9-b72e-49fd-86ca-815bb77c2481-1476458496665@3capp-gmx-bs30> (raw)
Hi there,
I'm currently debugging the 32 bit Linux Kernel 4.8.1 remotely with GDB and Qemu i386 2.7. My GDB script looks like this:
target remote localhost:10000
source .
symbol-file vmlinux
set width 0
set height 0
set verbose off
b rest_init
commands
continue
end
b console_init
commands
continue
end
b start_kernel
commands
continue
end
b startup_32
commands
continue
end
continue
Now apparently I'm missing something, since the breakpoints in C land, that is start_kernel, console_init, rest_init are recognized as breakpoints and thus jumped at by GDB just fine.
What does not work is the breakpoint on startup_32, which is still in Assembly land. GDB just jumps over it as if it wasn't called, but it is definitely called since it's the 32-bit kernel entrypoint.
Is this due to some real-mode/protected-mode fiddlings?
Best regards,
J.
next reply other threads:[~2016-10-14 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 15:21 deffo [this message]
2016-10-17 11:46 ` Yao Qi
2016-10-18 19:47 ` Jan Kratochvil
2016-10-18 16:53 deffo
2016-10-18 19:19 ` Yao Qi
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=trinity-155e70d9-b72e-49fd-86ca-815bb77c2481-1476458496665@3capp-gmx-bs30 \
--to=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