From: Daniel Jacobowitz <drow@false.org>
To: Pedro Alves <pedro_alves@portugalmail.pt>
Cc: gdb-patches@sourceware.org
Subject: Re: TUI + gdbserver broken?
Date: Mon, 19 Mar 2007 22:14:00 -0000 [thread overview]
Message-ID: <20070319221430.GA24326@caradoc.them.org> (raw)
In-Reply-To: <45FEF7B0.9070209@portugalmail.pt>
On Mon, Mar 19, 2007 at 08:50:56PM +0000, Pedro Alves wrote:
> Is TUI testable?
Probably, but it would require someone comfortable with expect to set
it up, I suspect.
> Since TUI is sitting on top of deprecated hooks, it TUI itself deprecated?
No.
> static void
> tui_selected_frame_level_changed_hook (int level)
> {
> struct frame_info *fi;
> fi = deprecated_safe_get_selected_frame ();
> /* Ensure that symbols for this frame are read in. Also, determine the
> source language of this frame, and switch to it if desired. */
> if (fi)
> {
> struct symtab *s;
How about this:
if (level >= 0)
{
struct frame_info *fi = get_selected_frame (NULL);
Insight wants to be notified even if there's no frame, apparently
(gross, I hate the way Insight is still attached at the hip to GDB -
I honestly believe that in a few years we'll have no choice but to
break Insight). But TUI doesn't.
> Here is an updated patch that also fixes the problem.
> The comments in the patch should make it obvious, and I think it does
> what you hinted at.
No, I meant at a higher level (i.e. why we were calling the hook).
The frame cache is supposed to be a cache - we should be able to
discard it at any and every time.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-03-19 22:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 1:53 Pedro Alves
2007-03-19 2:11 ` Daniel Jacobowitz
2007-03-19 15:58 ` Denis PILAT
2007-03-27 20:09 ` Daniel Jacobowitz
2007-04-17 15:48 ` [RFA] TUI is broken under Solaris Denis PILAT
2007-04-17 15:51 ` Daniel Jacobowitz
2007-04-18 8:24 ` Denis PILAT
2007-03-19 21:43 ` TUI + gdbserver broken? Pedro Alves
2007-03-19 22:14 ` Daniel Jacobowitz [this message]
2007-03-19 23:31 ` Pedro Alves
2007-03-19 23:41 ` Daniel Jacobowitz
2007-03-20 0:39 ` Pedro Alves
2007-03-20 2:56 ` Daniel Jacobowitz
2007-03-20 9:05 ` Pedro Alves
2007-03-20 23:21 ` Pedro Alves
2007-03-22 2:51 ` Pedro Alves
2007-03-27 20:15 ` Daniel Jacobowitz
2007-03-29 2:26 ` Pedro Alves
2007-03-29 18:55 ` Daniel Jacobowitz
[not found] <45F7480C.5010207@portugalmail.pt>
2007-03-14 8:29 ` Denis PILAT
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=20070319221430.GA24326@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro_alves@portugalmail.pt \
/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