public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: mckennad@esatclear.ie
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: Plugins : Memory Reads
Date: Tue, 27 May 2003 17:25:00 -0000	[thread overview]
Message-ID: <1054056649.1570.39.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <3ed39958.1ca4.0@esatclear.ie>

On Tue, 2003-05-27 at 09:59, David Mc Kenna wrote:

> Unfortunately this reads information in table format and as such I cannot read
> several different non consecutive locations and place them in the same table
> to be displayed by Insight. Is there an alternate command/method available that
> can be used to read memory which can then be place into the table structure?

I'm afraid I don't understand your problem. You want to read several
non-consecutive memory addresses and stuff them into some sort of table
widget?

If the table is displaying non-contiguous regions of memory (or just a
byte here and a byte there), it seems that you ought to be able to
accomplish this by passing gdb_update_mem a private array. Then your
plugin code could grab the interesting bits and stuff them into the
table.

So for the same table widget that the memory window uses, you would copy
the interesting bits into another data array that the widget uses. Since
the memory window only shows contiguous regions of memory, it has the
luxury of sharing one array across the call.

Of course, it would be a lot better if we had a specific (and simpler)
call for a memory read for plugins. I'm sure there are other areas where
we could serve plugins better, too...

Keith


  reply	other threads:[~2003-05-27 17:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-27 16:59 David Mc Kenna
2003-05-27 17:25 ` Keith Seitz [this message]
     [not found] <3ed46a5f.2d50.0@esatclear.ie>
2003-05-29  0:23 ` Keith Seitz

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=1054056649.1570.39.camel@lindt.uglyboxes.com \
    --to=keiths@redhat.com \
    --cc=insight@sources.redhat.com \
    --cc=mckennad@esatclear.ie \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).