From: "Shaolin Zhang" <zhangshaolin@huawei.com>
To: <linux-mips@oss.sgi.com>
Cc: "Ernest Jih" <ernest.jih@idt.com>, "\"recc stone\"" <renwei@huawei.com>
Subject: kgdb with linux-mips problem
Date: Wed, 19 Sep 2001 10:42:08 +0800 [thread overview]
Message-ID: <00fe01c140b4$ad3f9200$cd22690a@huawei.com> (raw)
Hello ,
Now we have some problems in using kgdb to debug the Linux-mips kernel on IDT 79s334A board.
1.I enabled the kernel startup option kgdb=on to debug the kernel setup.
At first, the gdb on host pc connected to the target boards correctly.
Then I use a few "n"(Next) command to debug the kernel, but the kernel
seems
to run out of my hands, as if I had executed some "c" command.
I use "set debug remote 1" command to see the packets gdb send&receive:
and find :
the gdb send a "c" packet to the stub at the end of packet sequence.
I guess that the gdb on the host pc send some wrong command , or it can't
get right info
to debug?
2.I want to debug some init_module function in module , like this :
int init_module(void)
{
breakpoint(); // use the breakpoint function in kernel to get a break.
my_functions();
}
When I insmod this module, it through exception 9 (breakpoint), then I run
"bt"
command in gdb, but this time gdb report "can't find the start of function
0x....".
Is this a gdb problem or gdb stub problem? BTW, when I first bootup the
kernel
and connect the gdb&stub ,the sample problem happened.
WARNING: multiple messages have this Message-ID (diff)
From: "Shaolin Zhang" <zhangshaolin@huawei.com>
To: linux-mips@oss.sgi.com
Cc: Ernest Jih <ernest.jih@idt.com>, "\"recc stone\"" <renwei@huawei.com>
Subject: kgdb with linux-mips problem
Date: Wed, 19 Sep 2001 10:42:08 +0800 [thread overview]
Message-ID: <00fe01c140b4$ad3f9200$cd22690a@huawei.com> (raw)
Message-ID: <20010919024208.W_44NbfIWW580kgf4_reBNHI8DUnQ5yA9ZZyFh8d1mg@z> (raw)
Hello ,
Now we have some problems in using kgdb to debug the Linux-mips kernel on IDT 79s334A board.
1.I enabled the kernel startup option kgdb=on to debug the kernel setup.
At first, the gdb on host pc connected to the target boards correctly.
Then I use a few "n"(Next) command to debug the kernel, but the kernel
seems
to run out of my hands, as if I had executed some "c" command.
I use "set debug remote 1" command to see the packets gdb send&receive:
and find :
the gdb send a "c" packet to the stub at the end of packet sequence.
I guess that the gdb on the host pc send some wrong command , or it can't
get right info
to debug?
2.I want to debug some init_module function in module , like this :
int init_module(void)
{
breakpoint(); // use the breakpoint function in kernel to get a break.
my_functions();
}
When I insmod this module, it through exception 9 (breakpoint), then I run
"bt"
command in gdb, but this time gdb report "can't find the start of function
0x....".
Is this a gdb problem or gdb stub problem? BTW, when I first bootup the
kernel
and connect the gdb&stub ,the sample problem happened.
next reply other threads:[~2001-09-19 2:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 2:42 Shaolin Zhang [this message]
2001-09-19 2:42 ` kgdb with linux-mips problem Shaolin Zhang
2001-09-19 2:46 ` Daniel Jacobowitz
2001-09-19 3:18 ` Shaolin Zhang
2001-09-19 3:18 ` Shaolin Zhang
2001-09-19 13:39 ` Daniel Jacobowitz
2001-09-19 13:39 ` Daniel Jacobowitz
2001-09-19 7:38 ` Kevin D. Kissell
2001-09-19 7:38 ` Kevin D. Kissell
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='00fe01c140b4$ad3f9200$cd22690a@huawei.com' \
--to=zhangshaolin@huawei.com \
--cc=ernest.jih@idt.com \
--cc=linux-mips@oss.sgi.com \
--cc=renwei@huawei.com \
/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