Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <Michael.Snyder@access-company.com>
To: Jeff Roberts <jeffr@radgametools.com>
Cc: gdb@sourceware.org
Subject: Re: technical question on GDB for MacOS
Date: Tue, 05 Jun 2007 18:01:00 -0000	[thread overview]
Message-ID: <1181066496.27951.2.camel@svmsnyderlnx.palmsource.com> (raw)
In-Reply-To: <307270C9C6214C9A883DE333F909D302@office.radgametools.com>

On Mon, 2007-06-04 at 14:42 -0700, Jeff Roberts wrote:
> > Right.  You can use "display/i $pc" and "x/i <addr>" to show the
> > assembly anyway.
> 
> Perfect, thank you!

Yes, the problem is that "disassemble" wants to do a whole function --
so it has to find symbols for the beginning and end of the function.
Self generated code doesn't have any symbols.

The examine /i command can take a start address and a repeat count
(number of instructions), eg "x/100i 0x1000"



  reply	other threads:[~2007-06-05 18:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-04  3:24 Jeff Roberts
2007-06-04 10:55 ` Daniel Jacobowitz
2007-06-04 21:43   ` Jeff Roberts
2007-06-05 18:01     ` Michael Snyder [this message]
2007-06-05 18:15       ` Andreas Schwab

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=1181066496.27951.2.camel@svmsnyderlnx.palmsource.com \
    --to=michael.snyder@access-company.com \
    --cc=gdb@sourceware.org \
    --cc=jeffr@radgametools.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