From: Daniel Jacobowitz <drow@false.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] DW_CFA_GNU_negative_offset_extended support
Date: Thu, 11 Jan 2007 20:02:00 -0000 [thread overview]
Message-ID: <20070111200224.GA27260@nevyn.them.org> (raw)
In-Reply-To: <20070111191107.GA4993@host0.dyn.jankratochvil.net>
On Thu, Jan 11, 2007 at 08:11:07PM +0100, Jan Kratochvil wrote:
> the patch is updated according to your advices.
Thanks. It may be a week or two before I have a chance to do patch
review again, unfortunately, but when I do I'll take care of this
(if no one gets there first).
> > Please use gdb_run_cmd instead. See other tests for an example.
> > ("run" doesn't work for remote targets.)
>
> Fixed. Copying other code just is not enough for GDB...
Yeah - some of the testsuite needs work, but it's low reward for the
effort when we could be fixing GDB instead.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-01-11 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-30 19:06 Jan Kratochvil
2007-01-03 18:27 ` Daniel Jacobowitz
2007-01-11 19:11 ` Jan Kratochvil
2007-01-11 20:02 ` Daniel Jacobowitz [this message]
2007-01-21 17:28 ` Daniel Jacobowitz
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=20070111200224.GA27260@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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