mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: min li <fly.limin@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: problems of using the 2.6.26 Linux Kernel Debugger (KGDB) with VMware
Date: Tue, 10 Nov 2009 14:55:54 +0800	[thread overview]
Message-ID: <7d98bfeb0911092255j1923ff6evafd9d40ee317d1d3@mail.gmail.com> (raw)

Hi everyone:
Recently I was using kgdb and VMware workstation to debug linux kernel 2.6.26.
I compiled and install kgdb according to the following webpage:
http://jaredrobinson.com/blog/using-the-2626-linux-kernel-debugger-kgdb-with-vmware/

But I still have some problems:
When I start gdb like:gdb ./vmliunx, it shows:

[root@localhost linux-2.6.26]# gdb ./vmlinux
GNU gdb Red Hat Linux (6.6-35.fc8rh)
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) set remotebaud 115200
(gdb) target remote /dev/ttyS0
Remote debugging using /dev/ttyS0
warning: shared library handler failed to enable breakpoint
0xc045516d in ?? ()

Then I type "n", it shows:
(gdb) n
Cannot find bounds of current function

I simply realize the output "0xc045516d in ?? ()" is different from
common output
"breakpoint () at kernel/kgdb.c:1212
1212:atomic_set(&kgdb_setting_breakpoint, 0);" which I found on some webpages

The real problem is that when I set breakpoints at like "sys_open",
"sys_getdents64", the kernel execution didn't stop at that point.
But if I "echo g > /proc/sysrq-trigger " in target machine, it can
stop running. In the development machine, I still only can send
"continue" command to make the target run again, if I send "next"
command, it shows just like above.

Does anybody confront this kind of problems, please give me some
suggestions, I really appreciate that!

--
Min Li
School of Computer Science and Technology
Cluster and Grid Computing Lab
Services Computing Technology and System Lab
Huazhong University of Science and Technology
Wuhan, 430074, China
Tel: +86-139-8625-1431
Email: fly.limin@gmail.com

                 reply	other threads:[~2009-11-10  6:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=7d98bfeb0911092255j1923ff6evafd9d40ee317d1d3@mail.gmail.com \
    --to=fly.limin@gmail.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®