public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Robert Bu" <robert.bu@gmail.com>
To: gdb@sourceware.org
Subject: It takes a long time to disassemble some instructions for remote target
Date: Wed, 14 Nov 2007 08:40:00 -0000	[thread overview]
Message-ID: <a0319f700711140039h1711df82p25ec50a94175ac2f@mail.gmail.com> (raw)

Hello all,

    When I try to disassemble a range of instructions, for example from
PC1 to PC2, GDB tries to fetch and disassemble the instructions one by
one. This may not be a problem for native debugging, or for remote
debugging with high connection speed. However, it takes some long time
for a not so fast serial connection, since GDB fetches one instruction
at a time, which results in a lot of 'm' packets.
    Is that possible for GDB to fetch all instructions back for one time
with just one(maybe more than one, but now a lot of) 'm' packet, and
disassemble them locally one by one?

Thanks.
Robert.
20071114

             reply	other threads:[~2007-11-14  8:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-14  8:40 Robert Bu [this message]
2007-11-14 11:53 ` Michael Snyder
2007-11-15  2:43 Robert Bu
2007-11-20  6:46 Robert Bu
2007-11-20 12:17 ` Michael Snyder

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=a0319f700711140039h1711df82p25ec50a94175ac2f@mail.gmail.com \
    --to=robert.bu@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).