From: Daniel Jacobowitz <drow@false.org>
To: Carlos Eduardo Rodrigues de Almeida <eduardo.almeida@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: Bug in MI command -data-dissasemble ??
Date: Fri, 03 Mar 2006 17:22:00 -0000 [thread overview]
Message-ID: <20060303172251.GA13669@nevyn.them.org> (raw)
In-Reply-To: <214135380603030921x67047848k4ad854dee2f09444@mail.gmail.com>
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.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-03-03 17:22 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 [this message]
2006-03-03 19:39 ` Carlos Eduardo Rodrigues de Almeida
2006-03-03 19:44 ` Daniel Jacobowitz
2006-03-03 20:11 ` Nick Roberts
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=20060303172251.GA13669@nevyn.them.org \
--to=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).