From: Stan Shebs <stan@codesourcery.com>
To: Bart Veer <bartv@ecoscentric.com>
Cc: gdb-patches@sourceware.org
Subject: Re: add file I/O support when debugging an embedded target via jtag
Date: Sun, 31 Aug 2008 14:36:00 -0000 [thread overview]
Message-ID: <48BAAC44.4000002@codesourcery.com> (raw)
In-Reply-To: <pnr685s96z.fsf@delenn.bartv.net>
Bart Veer wrote:
> Following on from
> http://sourceware.org/ml/gdb-patches/2008-08/msg00315.html, I have not
> heard anything about the code in the last two weeks. Do you know if
> anybody is looking at it? Also, if there is a likelihood that the
> patch will be accepted then I should probably get started on the
> assignment paperwork.
>
To be honest, I looked at it but didn't understand why all this stuff
seemed necessary. If this is not for the remote protocol, then what is
it for? A target supported by GDB, or something else? The addition of
another stratum raises alarm bells with me, because the stratums are not
as orthogonal as they should be, and I wouldn't be surprised if other
configurations were broken by this. Also, how will everybody
regression-test this (read: "make check") to know that other changes
haven't broken this code?
Stan
next prev parent reply other threads:[~2008-08-31 14:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 16:34 Bart Veer
2008-08-12 19:08 ` Eli Zaretskii
2008-08-31 11:42 ` Bart Veer
2008-08-31 14:36 ` Stan Shebs [this message]
2008-08-31 15:39 ` Bart Veer
2008-09-23 10:15 ` Bart Veer
2008-09-23 12:03 ` Doug Evans
2008-09-24 21:21 ` Bart Veer
2008-09-25 17:05 ` Doug Evans
2008-09-25 20:27 ` Bart Veer
2008-09-25 22:20 ` Daniel Jacobowitz
2008-10-01 18:39 ` Bart Veer
2008-10-01 21:10 ` Daniel Jacobowitz
2008-10-09 17:11 ` Bart Veer
2008-10-17 11:59 ` John Dallaway
2008-09-01 3:07 ` Eli Zaretskii
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=48BAAC44.4000002@codesourcery.com \
--to=stan@codesourcery.com \
--cc=bartv@ecoscentric.com \
--cc=gdb-patches@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