From: loody <miloody@gmail.com>
To: Keith Seitz <keiths@redhat.com>
Cc: insight@sourceware.org
Subject: Re: how to add additional script to add more register information
Date: Wed, 23 Jan 2013 16:31:00 -0000 [thread overview]
Message-ID: <CANudz+sCo2oaRrcqA9MubiKBuain3G579jFAO_EnujvGWanQ0w@mail.gmail.com> (raw)
In-Reply-To: <50F038A5.2010606@redhat.com>
hi Keith:
2013/1/12 Keith Seitz <keiths@redhat.com>:
> On 01/11/2013 07:53 AM, loody wrote:
>>
>> hi all:
>> is it possible to add additional script to add information I want in
>> insight?
>
>
> It is possible, yes. Easy? Maybe not so much.
>
>
>> if it could, is there any example i can follow?
>
>
> There are two ways to accomplish your specific task.
>
> First, the ugly, but more integrated way, is to hack at
> gdbtk/library/regwin.it[hb]. The code there is actually fairly recent and
> clean.
>
> The more formal way, but less integrated, is to create a plug-in. To do
> that, follow the directions in gdbtk/library/plugins/HOW-TO. WARNING: I
> haven't looked at these directions in quite some time, they may be slightly
> outdated. But I doubt much has changed since there have been no plug-ins
> written in a very long time. If you find problems with the HOW-TO, just send
> a note to this list so that I can address them.
>
> In lieu of that, or in addition to that, you can follow the either the
> example plug-in (gdbtk/library/plugins/rhabout) and/or the (very simple)
> Pentium plug-in (gdbtk/library/plugins/intel-pentium).
>
> Again, if you run into problems or have any questions, just send a note to
> this list, and I'll try to get your questions answered as best as possible.
Sorry for late response your mail.
should I get any script familiar fist, such tcl?
if tcl learning is necessary, where I can get it?
Thanks a lot,
--
Regards,
next prev parent reply other threads:[~2013-01-23 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 15:53 loody
2013-01-11 16:07 ` Keith Seitz
2013-01-23 16:31 ` loody [this message]
2013-01-23 17:08 ` Keith Seitz
2013-01-24 15:51 ` loody
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=CANudz+sCo2oaRrcqA9MubiKBuain3G579jFAO_EnujvGWanQ0w@mail.gmail.com \
--to=miloody@gmail.com \
--cc=insight@sourceware.org \
--cc=keiths@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).