Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: loody <miloody@gmail.com>
To: gdb@sourceware.org
Subject: some questions about gdb
Date: Sat, 08 Jan 2011 13:50:00 -0000	[thread overview]
Message-ID: <AANLkTin8xB8Z=LZisyd2f8jCi6jPmOSr_e9hRRb4en_v@mail.gmail.com> (raw)

hi all:
I have some questions about using gdb
1. I compile the kernel with -g but I cannot see the disassembly.
My pc increase 4 when I type 'n' but I cannot see the disassembly.

Program received signal 0, Signal 0.
0x8043e59c in kernel_entry () at arch/mips/kernel/head.S:97
97	#else
(gdb) n

Program received signal 0, Signal 0.
0x8043e5a0 in kernel_entry () at arch/mips/kernel/head.S:97
97	#else
(gdb) si

Program received signal 0, Signal 0.
0x8043e5a4 in kernel_entry () at arch/mips/kernel/head.S:97
97	#else
(gdb)

Did I miss any configuration?

2. I search gdb and which tell me there is a command, disassemble /m,
which can mix source and assembly.
But I use it on my mips platform, it said:
(gdb) disassemble /m irq_enter
A syntax error in expression, near `/m'.
(gdb) list
276     void irq_enter(void)
277     {
278             int cpu = smp_processor_id();
279
280             rcu_irq_enter();
281             if (idle_cpu(cpu) && !in_interrupt()) {
282                     __irq_enter();
283                     tick_check_idle(cpu);
284             } else
285                     __irq_enter();
(gdb)

3. is any document about how to compile insight6.8.1 with mips gdb 7.2?
I google it and I found for arm version
http://old.nabble.com/patch-for-insight-6.8.1-to29485252.html
if I do the same thing for mips gdb, should I patch gdb?


-- 
Thanks for your help,
miloody


             reply	other threads:[~2011-01-08 13:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-08 13:50 loody [this message]
2011-01-08 14:14 ` loody
2011-01-10 20:58 ` Tom Tromey
2011-01-10 21:47   ` Keith Seitz
2011-01-16 13:47     ` loody
2011-01-17 17:16       ` Tom Tromey
2011-01-16 19:03     ` Petr Hluzín

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='AANLkTin8xB8Z=LZisyd2f8jCi6jPmOSr_e9hRRb4en_v@mail.gmail.com' \
    --to=miloody@gmail.com \
    --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