From: Keith Seitz <kseitz@firetalk.com>
To: Paul Breed <pbreed@yahoo.com>
Cc: insight@sourceware.cygnus.com
Subject: Re: results insight script init...
Date: Mon, 17 Jul 2000 05:30:00 -0000 [thread overview]
Message-ID: <3972FC64.ADE256EF@firetalk.com> (raw)
In-Reply-To: <20000715143607.18927.qmail@web3505.mail.yahoo.com>
Paul Breed wrote:
>
> My Goal was to have Insight automatically connect
> to a specific target on startup and to prevent
> the attach dialog when you hit run.
>
> I have it all working my gdb.ini file:
>
> symbol-file DBdebugdemo.elf
> set remotebaud 57600
> set remotedevice COM1
> target remote COM1
> tk set ::gdb_target_name remote
> tk gdbtk_update
> tk gdbtk_next
> tk gdbtk_update
> tk gdbtk_idle
>
> The only problem remaining is that the cursor in
> the code window is an hourglass, and not a pointer.
>
This normally occurs as part of the idle callbacks (invoked with
gdbtk_idle). Perhaps you simply need to add gdbtk_idle call to an "after
idle" or something. (I dunno, actually. I am working on a similar
problem myself...)
> I believe that this can be fixed with
> SrcWin::enable_ui { on }
> or
> SrcWin::no_inferior
>
> But how do I get an instance of the source window?
>
One question first: can you type into the console window? If so, then
you've probably found a bug in one of the idle or update callbacks.
Using "gdbtk_idle" will cause all windows to go "idle", ready for user
input.
Now onto the real question. You can use the proc "ManagedWin::find
className" to find a window of the given classname. So you would use
"ManagedWin::find Src". This will return a list of all the objects of
class "Src". It could be one, it could be many.
Keith
prev parent reply other threads:[~2000-07-17 5:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-15 7:36 Paul Breed
2000-07-17 5:30 ` Keith Seitz [this message]
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=3972FC64.ADE256EF@firetalk.com \
--to=kseitz@firetalk.com \
--cc=insight@sourceware.cygnus.com \
--cc=pbreed@yahoo.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).