From: Daniel Jacobowitz <drow@false.org>
To: Bart Veer <bartv@ecoscentric.com>
Cc: Doug Evans <dje@google.com>,
stan@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: add file I/O support when debugging an embedded target via jtag
Date: Thu, 25 Sep 2008 22:20:00 -0000 [thread overview]
Message-ID: <20080925222009.GA8202@caradoc.them.org> (raw)
In-Reply-To: <pnabdwrmyx.fsf@delenn.bartv.net>
On Thu, Sep 25, 2008 at 09:26:30PM +0100, Bart Veer wrote:
> Although I have no doubt that a Python interface at the target vector
> level is possible, figuring out what such an interface should look
> like requires a far greater understanding of the gdb internals than I
> possess. I am pretty sure it would also involve much bigger changes to
> the internals than a one-line addition to the stratum enum. I really
> don't want to see the h/w debug I/O functionality to be delayed for a
> long time, possibly years, until all the required infrastructure is in
> place for a reimplementation in Python.
This is a reasonable argument. Unfortunately the other direction is
reasonable too: remember Stan's comment about adding new strata?
That's got maintenance cost for the rest of GDB, because the strata
aren't really meant to work this way. And it may get in the way of
future development, e.g. the work that Stan and Pedro are doing to
support multiple processes and multi-core systems.
FWIW, I find your reason for putting it above process_stratum
convincing but not your reason for putting it below thread_stratum.
I don't see why it has to be in the target vector at all.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-09-25 22:20 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
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 [this message]
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=20080925222009.GA8202@caradoc.them.org \
--to=drow@false.org \
--cc=bartv@ecoscentric.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=stan@codesourcery.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