From: Marco Schramel <Schramel.Linux@go.bartec.de>
To: "PPC_LINUX" <linuxppc-embedded@lists.linuxppc.org>
Subject: BDI kernel debug
Date: Tue, 6 Jul 2004 13:31:08 +0200 [thread overview]
Message-ID: <200407061331.08613.Schramel.Linux@go.bartec.de> (raw)
Hi all,
i have some problems with debugging my kernel. This is the first time i use bdi for kernel debugging. ELDK 3.0 is my toolchain (Target 8270).
My bdi2000 can sync with the gdb (ddd) debugger.
I let the kernel run until "start_here", at example. Then i try to step through the source. I see the source and i can step in it. Sometimes it happens that i spend a lot of time in
linux/kernel/timer.c. Then the output of gdb is "
(gdb) next
Single stepping until exit from function __cli,
which has no line number information.
Program received signal SIGSTOP, Stopped (signal).
0xc0007dec in __cli ()"
The same output with "step". "Cont" ends also there, although i had set a breakpoint later in the source.
Are there some options in the kernel or in the gdb to set ?
Thanks in advance
Marco
---------
Marco Schramel
R&D
Bartec GmbH
Schulstr. 30
94239 Gotteszell, Germany
www.bartec.de
Marco.Schramel@go.bartec.de
Phone: +49 (0)9929/301332
Fax: +49 (0)9929/301112
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-07-06 11:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 11:31 Marco Schramel [this message]
2004-07-06 18:18 ` BDI kernel debug Wolfgang Denk
2004-07-07 5:01 ` Marco Schramel
2004-07-07 11:42 ` Fahd Abidi
2004-07-07 11:52 ` Marco Schramel
[not found] <81C69D96BDD30640952C7A404004AA250C2CA8@h0007e95d9fa7.ne.client2.attbi.com>
2004-07-07 13:07 ` Fahd Abidi
2004-07-08 14:03 ` Marco Schramel
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=200407061331.08613.Schramel.Linux@go.bartec.de \
--to=schramel.linux@go.bartec.de \
--cc=linuxppc-embedded@lists.linuxppc.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).