From: Daniel Jacobowitz <drow@false.org>
To: Michael Eager <eager@eagercon.com>
Cc: gdb@sources.redhat.com
Subject: Re: Upgrading from old gdb version
Date: Mon, 05 Mar 2007 01:46:00 -0000 [thread overview]
Message-ID: <20070305014619.GA19913@caradoc.them.org> (raw)
In-Reply-To: <45EB3B6A.30504@eagercon.com>
On Sun, Mar 04, 2007 at 01:34:34PM -0800, Michael Eager wrote:
> Can someone suggest a starting point?
Not really - last time I had to do this, I found it easiest to take a
working target from the current GDB and redo my older port based on
that model.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-03-05 1:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 21:34 Michael Eager
2007-03-05 1:46 ` Daniel Jacobowitz [this message]
2007-03-05 18:22 ` Jim Blandy
2007-03-05 19:26 ` Michael Eager
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=20070305014619.GA19913@caradoc.them.org \
--to=drow@false.org \
--cc=eager@eagercon.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