Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] -data-list-changed-registers
Date: Fri, 03 Jun 2005 22:36:00 -0000	[thread overview]
Message-ID: <20050603223652.GA8203@nevyn.them.org> (raw)
In-Reply-To: <17056.56149.181259.513462@farnswood.snap.net.nz>

On Sat, Jun 04, 2005 at 10:36:05AM +1200, Nick Roberts wrote:
> Daniel Jacobowitz writes:
>  > On Wed, Jun 01, 2005 at 11:12:01PM +1200, Nick Roberts wrote:
>  > > 
>  > > Currently the GDB/MI command -data-list-changed-registers gives an internal
>  > > error if there is no stack i.e when there is no inferior process:
>  > 
>  > This has come up before; the right solution is elsewhere.  I believe
>  > that updating register_changed_p and get_register to use
>  > get_selected_frame() will work.
>  > 
>  > I have a big patch for this sort of thing lying around, but the problem
>  > is that many of the references to deprecated_selected_frame should
>  > really by fixed by adding a frame parameter to the function, so that
>  > they can be used on non-selected frames.  They need to be looked over
>  > one by one and I haven't gotten round to it yet.
> 
> Could this patch be applied as an interim measure? Currently any front end
> that uses -data-list-changed-registers without a stack crashes.

I would prefer not to; right now the presence of
deprecated_selected_frame is a good warning sign.  I can find you a
copy if you want to look at individual places that should be
investigated.

I think the changes are right in this case, though.  Could you take a
look at those two functions (the change to make is obvious) and see if
that fixes your problem?

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-06-03 22:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01 11:12 Nick Roberts
2005-06-03 19:13 ` Daniel Jacobowitz
2005-06-03 22:35   ` Nick Roberts
2005-06-03 22:36     ` Daniel Jacobowitz [this message]
2005-06-04 11:41       ` Nick Roberts
2005-06-06 20:44         ` Nick Roberts
2005-06-11  5:54           ` Nick Roberts
2005-06-11  6:50           ` [PATCH] -data-list-changed-registers (Take 2) Nick Roberts
2005-06-13  2:40             ` Daniel Jacobowitz
2005-06-13  4:47               ` Nick Roberts
2005-06-13 13:48                 ` Daniel Jacobowitz
2005-06-13 22:38                   ` Nick Roberts
2005-06-13 22:42                     ` Daniel Jacobowitz
2005-06-14  2:45                       ` Nick Roberts
2005-06-17  1:51                         ` Daniel Jacobowitz
2005-06-17  3:13                           ` Nick Roberts
2005-06-17  3:22                             ` Daniel Jacobowitz

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=20050603223652.GA8203@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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