Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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 02:11:00 -0000	[thread overview]
Message-ID: <20070319021145.GA25872@caradoc.them.org> (raw)
In-Reply-To: <45FDECB3.5000002@portugalmail.pt>

Thanks for all your detective work on this.  I'm sorry I apparently
broke TUI so badly - I wish we had test coverage.

On Mon, Mar 19, 2007 at 01:51:47AM +0000, Pedro Alves wrote:
> The problem is that we now call deprecated_safe_get_selected_frame
> in tui_selected_frame_level_changed_hook... :

Before I look at your patch, could you check one more thing for me:
what's the backtrace look like when we get here?

> The attached patch fixes it by calling target_mark_running, and
> target_mark_exited in remote.c.  These functions set those
> target_has_* to 0 and 1 appropriately.  They are currently only
> used on remote-sim.c.  Let me know if there is a better way to
> know if the target is running.

I think it is more likely that we shouldn't be doing whatever we're
doing until after we've finished cleaning up the target's state.
It's stuck between wait and mourn.

> tui_registers_changed_hook then has the problem that is is calling
> get_selected_frame, when target_has_registers is false.  Fixed by
> using deprecated_safe_get_selected_frame here too.

This bit makes sense; you can commit it separately if you want.


-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-03-19  2:11 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 [this message]
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
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=20070319021145.GA25872@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