From: Heiko Gerdau <hg@technosis.de>
To: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: Insight 6.0 and Dlls
Date: Sat, 07 Feb 2004 16:51:00 -0000 [thread overview]
Message-ID: <200402071749.47602.hg@technosis.de> (raw)
In-Reply-To: <1076005443.1587.67.camel@lindt.uglyboxes.com>
On Thursday 05 February 2004 19:24, Keith Seitz wrote:
> On Thu, 2004-02-05 at 07:41, Heiko Gerdau wrote:
> If you look at symbol_file_add now, we see that the
> pre/post_add_symbol_hooks are ONLY called if from_tty != 0 or "info
> verbose" has been set.
>
> Now, I cannot tell you that setting "info verbose" in gdb proper will
> not interfere with insight, but I do think that there is a fundamental
> problem with the hooks not being called in this case.
>
> Should from_tty be non-zero? I don't know.
> Should the hooks be called no matter what? I don't remember. I have
> vague recollections that there was a reason for the from_tty thing. :-(
>
> I've run through the CVS history, and I see that SOLIB_ADD has always
> had from_tty set to 0. Yet I remember clearly that this used to work.
> From the looks of it, it would appear that this shouldn't work on unix,
> either.
>
> Well, that's all I have right now. You migt as well try setting info
> verbose and seeing if that helps works around it for now.
Thanks for pointing this out. If I do the two changes below in function
"symbol_file_add_with_addrs_or_offsets" in symfile.c the insight combobox
is blinking heavily on startup but gets all the source files from all the
libraries with debugginjg information.
I commented out:
lines 887 and 963 in symfile.c each containing
/* if (from_tty || info_verbose) */
Thanks
Heiko
prev parent reply other threads:[~2004-02-07 16:51 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
2004-02-05 15:43 ` Heiko Gerdau
2004-02-05 18:19 ` Keith Seitz
2004-02-07 16:51 ` Heiko Gerdau [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=200402071749.47602.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).