From: Jim Blandy <jimb@red-bean.com>
To: John Williams <jwilliams@itee.uq.edu.au>
Cc: gdb@sourceware.org
Subject: Re: Triggering qSymbol packets
Date: Thu, 19 Jan 2006 01:18:00 -0000 [thread overview]
Message-ID: <8f2776cb0601181701p150929ccldf9465a6e368ecdf@mail.gmail.com> (raw)
In-Reply-To: <43CEE12E.90504@itee.uq.edu.au>
On 1/18/06, John Williams <jwilliams@itee.uq.edu.au> wrote:
> OK. I'm guessing a back-port of the fixup will be much easer (short
> term) than a forward port of the entire arch. Am I maybe
> over-estimating the work involved in migrating an arch from gdb 5.3 to 6.4?
A lot has changed. The frame unwinding interface is eccentric in a
different way than it used to be. :) Actually, it's much more
well-defined, and well-behaved. The gdbarch methods for calling
functions and extracting their return values have changed. So there's
a lot of work entailed in bringing a port forward.
next prev parent reply other threads:[~2006-01-19 1:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 0:19 John Williams
2006-01-19 0:46 ` Daniel Jacobowitz
2006-01-19 0:50 ` John Williams
2006-01-19 1:18 ` Jim Blandy [this message]
2006-01-19 3:26 ` Daniel Jacobowitz
2006-01-20 4:42 ` John Williams
2006-01-20 20:29 ` Jie Zhang
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=8f2776cb0601181701p150929ccldf9465a6e368ecdf@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=gdb@sourceware.org \
--cc=jwilliams@itee.uq.edu.au \
/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