From: renwei <renwei@huawei.com>
To: linux-mips@linux-mips.org
Subject: gdb/insight 5.3 buggy in kernel module debug
Date: Tue, 08 Jul 2003 16:00:08 +0800 [thread overview]
Message-ID: <003501c34526$f5adfcc0$6efc0b0a@huawei.com> (raw)
Is there anyone else find the same problem?
I download the gdb/insight 5.3 , want to use
it to debug my mipsel idt334 board.
configure as --target=mipsel-linux.
when connect to the target , it always give me
some wrong addr:
new thead xxxxxx
0xffffffff83f28040 in ??()
something like that.
and the backtrace command can't work, also.
but my gdb5.0 for mipsel is ok.
I think that's the gdb get the pc as 64bit, but my
board's cpu is 32bit, so it can't get the correct pc ...
The kernel addr is up to 0x80000000, so it's negative.
I trace the gdb5.3 , and find the place in
mips-tdep.c, so I just fix the read_pc , make it
as 32bit , now it can work, and the backtrace command
can display the call trace .
But I'm not sure if my fix is a full one ?
Anyone have full patch please tell me ...
renc
next reply other threads:[~2003-07-08 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-08 8:00 renwei [this message]
2003-07-09 12:36 ` gdb/insight 5.3 buggy in kernel module debug Ralf Baechle
2003-07-11 2:14 ` [patch]: " renwei
2003-07-11 2:31 ` Ralf Baechle
2003-07-11 2:43 ` Daniel Jacobowitz
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='003501c34526$f5adfcc0$6efc0b0a@huawei.com' \
--to=renwei@huawei.com \
--cc=linux-mips@linux-mips.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