public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Heiko Gerdau <hg@technosis.de>
To: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: Insight 6.0 and Dlls
Date: Sat, 24 Jan 2004 00:27:00 -0000	[thread overview]
Message-ID: <200401240126.26418.hg@technosis.de> (raw)
In-Reply-To: <1074696965.1591.18.camel@lindt.uglyboxes.com>

On Wednesday 21 January 2004 15:56, Keith Seitz wrote:
> On Tue, 2004-01-06 at 06:05, Heiko Gerdau wrote:
> > The problem: After running the programm and breaking in main insight
> > should have access to the dll symbols and sources but does not show
> > them in the dropdown list of available source files.
>
> I think that the real problem is that Insight doesn't get any
> library-loaded events. Nonetheless, I thought that I'd worked around
> this problem by restuffing the source window's combo boxes whenever we
> read symbols.
>
> I can see in src/gdb/gdbtk/library/interface.tcl that the procedure
> gdbtk_tcl_post_add_symbol does, indeed, attempt to refill the combo
> boxes. Is this not being called when the shared library is loaded (You
> can put a "puts" in there or a debug statement that will show up in the
> debug window)?

gdbtk_tcl_post_add_symbol seems to be never called. At least I can't see 
any output from my puts and debug statements at any time.

Just to make sure: I have also put some similar debug statements into the 
function fillNameCB and I see those messages only from the combobox 
filling at startup.

Greetings
Heiko

  reply	other threads:[~2004-01-24  0:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-06 14:06 Heiko Gerdau
2004-01-21 14:51 ` Keith Seitz
2004-01-24  0:27   ` Heiko Gerdau [this message]
2004-02-05 15:43     ` Heiko Gerdau
2004-02-05 18:19       ` Keith Seitz
2004-02-07 16:51         ` Heiko Gerdau

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=200401240126.26418.hg@technosis.de \
    --to=hg@technosis.de \
    --cc=insight@sources.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).