From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: Carlos Eduardo Rodrigues de Almeida <eduardo.almeida@gmail.com>,
gdb@sources.redhat.com
Subject: Re: Bug in MI command -data-dissasemble ??
Date: Fri, 03 Mar 2006 20:11:00 -0000 [thread overview]
Message-ID: <17416.41608.570147.885292@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20060303172251.GA13669@nevyn.them.org>
Daniel Jacobowitz writes:
> On Fri, Mar 03, 2006 at 02:21:09PM -0300, Carlos Eduardo Rodrigues de Almeida wrote:
> > Hi all,
> > I'll try to figure out what is going on.. Is there some document that
> > describes the organization of the GDB code?? Is there some place where
> > I can grab more information?
>
> There's the GDB internals manual (gdbint.texinfo, format it as info or
> pdf or whatever's convenient for you); but, I don't think it has much
> to say about MI issues.
But I suspect (possibly ignorantly) that the underlying problem is to do with
symbol table information, which the internals manual does describe. An easy
way to test this might be to look at the output of of the CLI command
disassemble. Anyway it looks like its not present in current CVS. Perhaps 64
bit operation is a recent feature.
--
Nick http://www.inet.net.nz/~nickrob
prev parent reply other threads:[~2006-03-03 20:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 4:03 Carlos Eduardo Rodrigues de Almeida
2006-03-03 0:51 ` Nick Roberts
2006-03-03 17:21 ` Carlos Eduardo Rodrigues de Almeida
2006-03-03 17:22 ` Daniel Jacobowitz
2006-03-03 19:39 ` Carlos Eduardo Rodrigues de Almeida
2006-03-03 19:44 ` Daniel Jacobowitz
2006-03-03 20:11 ` Nick Roberts [this message]
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=17416.41608.570147.885292@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=eduardo.almeida@gmail.com \
--cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).