From: xingxing pan <forandom@gmail.com>
To: Doug Evans <dje@google.com>
Cc: gdb <gdb@sourceware.org>
Subject: Re: Which version of binutils matches the BFD and Opcode in GDB6.8?
Date: Tue, 15 Sep 2009 13:38:00 -0000 [thread overview]
Message-ID: <77f815bd0909150638s49b0ce27g722a005384f495a6@mail.gmail.com> (raw)
In-Reply-To: <e394668d0909150624i2b407a2q35502a8a1ef89fd2@mail.gmail.com>
You mean there are two groups of people maintain the bfd/opcode
respectively? Why not use one bfd/opcode? What's the difference?
2009/9/15 Doug Evans <dje@google.com>:
> On Tue, Sep 15, 2009 at 6:19 AM, xingxing pan <forandom@gmail.com> wrote:
>> Are the BFD and Opcode in GDB6.8 from the binutils or developed
>> separately from binutils?
>
> Depends on what you mean by "separate". :-)
>
> They do come from the same source tree, and so are not separate in
> that sense, *but* they are released at different times, and so one
> can't, technically, match bfd/opcodes from a binutils release with the
> ones in a gdb release.
>
next prev parent reply other threads:[~2009-09-15 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 13:19 xingxing pan
2009-09-15 13:24 ` Doug Evans
2009-09-15 13:38 ` xingxing pan [this message]
2009-09-15 15:47 ` Doug Evans
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=77f815bd0909150638s49b0ce27g722a005384f495a6@mail.gmail.com \
--to=forandom@gmail.com \
--cc=dje@google.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