Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Keith Seitz <keiths@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] stack.c: Always set current_source_{symtab,line}
Date: Mon, 26 Aug 2002 15:57:00 -0000	[thread overview]
Message-ID: <1020826225235.ZM333@localhost.localdomain> (raw)
In-Reply-To: Keith Seitz <keiths@redhat.com> "Re: [RFA] stack.c: Always set current_source_{symtab,line}" (Aug 22, 11:05am)

On Aug 22, 11:05am, Keith Seitz wrote:

> Ping.
> 
> On Wed, 14 Aug 2002, Keith Seitz wrote:
> 
> > Hi,
> > 
> > Another MI fallout. This has changed a few times in the past few months, 
> > but I believe that this is how it should be for anything that uses the 
> > CLI/command interpreter.
> > 
> > Without this, an -interpreter-exec call in MI will get "lost". (Use MI to 
> > stop at breakpoint, step a few times, use console interp to "break" -- 
> > breakpoint would be set someplace other than current location.)
> > 
> > I've run this through the testsuite, and it introduces no new failures. 
> > (And of course, it still works with Insight.)
> > 
> > Keith
> > 
> > ChangeLog
> > 2002-08-14  Keith Seitz  <keiths@redhat.com>
> > 
> >         * stack.c (print_frame_info_base): Always set current_source_symtab
> >         and current_source_line.

Keith,

I don't claim any deep understanding of the code affected, but I've
looked over your patch and it seems reasonable to me.

Kevin


  reply	other threads:[~2002-08-26 22:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-14 16:25 Keith Seitz
2002-08-22 11:09 ` Keith Seitz
2002-08-26 15:57   ` Kevin Buettner [this message]
2002-08-29  8:07 ` Elena Zannoni
2002-08-29  9:10   ` Keith Seitz
2002-08-29 12:32     ` Elena Zannoni
2002-08-29 12:43       ` Keith Seitz
2002-08-29 12:54         ` Elena Zannoni
2002-08-29 13:16           ` Keith Seitz
2002-08-29 20:28     ` Elena Zannoni
2002-08-30 11:12       ` Keith Seitz
2002-08-30 12:44         ` Andrew Cagney
2002-08-30 12:57           ` Keith Seitz

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=1020826225235.ZM333@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=keiths@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