This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: add file I/O support when debugging an embedded target via jtag
- From: "Doug Evans" <dje at google dot com>
- To: "Bart Veer" <bartv at ecoscentric dot com>
- Cc: stan at codesourcery dot com, gdb-patches at sourceware dot org
- Date: Tue, 23 Sep 2008 05:02:53 -0700
- Subject: Re: add file I/O support when debugging an embedded target via jtag
- References: <pn4p5quran.fsf@delenn.bartv.net> <ubpzygigj.fsf@gnu.org> <pnr685s96z.fsf@delenn.bartv.net> <48BAAC44.4000002@codesourcery.com> <pnod39ry8d.fsf@delenn.bartv.net> <pnr67brwxa.fsf@delenn.bartv.net>
On Tue, Sep 23, 2008 at 3:14 AM, Bart Veer <bartv@ecoscentric.com> 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.
>
> Stan> To be honest, I looked at it but didn't understand why all
> Stan> this stuff seemed necessary. If this is not for the remote
> Stan> protocol, then what is it for? A target supported by GDB, or
> Stan> something else?
>
> Bart> The rationale was given in
> Bart> http://sourceware.org/ml/gdb/2008-07/msg00045.html
>
> <snip>
>
> Just wondering if you had had a chance to take another look at this.
> It has now been six weeks since the original posting.
Hi. fwiw, I've read the patch and past emails. fwiw, I love the idea but
wonder if it should be done differently. Adding a new stratum feels
wrong to me too. But maybe I'm missing something so let me first ask
a question. Basically all you need is a way to run some special code
when a particular breakpoint is hit, right? [There's some housekeeping
like needing to intercept program loads (IIRC), but basically the high
order bit is running special code when a particular breakpoint is hit,
right?] I'm just wondering if this can be done differently without being
as invasive on GDB's innards. My off-the-cuff thought is to see if this
is something that could be handled from Python.