Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Jason Molenda <jason-swarelist@molenda.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Adding -file-list-exec-source-file command to GDB/MI
Date: Mon, 31 Mar 2003 20:12:00 -0000	[thread overview]
Message-ID: <3E88A13D.6010405@redhat.com> (raw)
In-Reply-To: <20030331112537.A73741@molenda.com>


> Ah, now I see.  You didn't mean "That doesn't work", you meant "That
> doesn't work generally".

"Generally" isn't the issue.  GDB needs changes that work.  As you note 
with #2

> #1 doesn't apply to us at Apple.  #2 is a real problem - although
> the failure mode is that the UI re-fetches the stack, so it's not
> too traumatic.  And because it only needs to re-fetch the 0th frame,
> it is fast.  And you'll have the same problem with varobj's being
> deleted when your FP moves IIRC.  

even for Apple, this doesn't work.

Per my original comment, and many previous posts, MI (varobj) needs to 
switch to frame IDs.

> As for #3, I don't understand why the PC won't remain constant for
> a frame other than the 0th, but you're familiar with far more
> architectures than me.  Obviously the currently executing frame
> will have a changing PC, but the frames higher up on the stack
> should stay constant unless they've executed some more.

The function address is needed when trying to correctly re-identify a 
frame that has executed.

Andrew


  reply	other threads:[~2003-03-31 20:12 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-20 22:44 Bob Rossi
2003-03-21  4:34 ` Eli Zaretskii
2003-03-21  9:53 ` Jason Molenda
2003-03-21 13:16   ` Bob Rossi
2003-03-28 15:26     ` Andrew Cagney
2003-03-30  4:06       ` Bob Rossi
2003-03-31  4:22         ` Andrew Cagney
2003-03-31  8:13           ` Jason Molenda
2003-03-31 14:31             ` Andrew Cagney
2003-03-31 17:16               ` Jason Molenda
2003-03-31 18:52                 ` Andrew Cagney
2003-03-31 19:20                   ` Jason Molenda
2003-03-31 20:12                     ` Andrew Cagney [this message]
2003-03-26 22:48 ` Andrew Cagney
2003-03-28 14:35   ` Bob Rossi
2003-03-28 15:30 ` Andrew Cagney
2003-03-28 16:05   ` Bob Rossi
2003-03-28 16:10     ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2003-04-02 20:24 Bob Rossi
2003-04-02 21:59 ` Andrew Cagney
2003-04-03  2:54 ` Eli Zaretskii
2003-04-02 20:24 Bob Rossi
2003-03-29  0:41 Bob Rossi
2003-03-31  5:38 ` Andrew Cagney
2003-03-31 18:46   ` Bob Rossi
2003-03-31 18:56     ` Andrew Cagney
2003-04-02 16:15   ` Bob Rossi
2003-04-02 16:27     ` Andrew Cagney
2003-03-10  0:31 Bob Rossi
2003-03-10  4:28 ` Eli Zaretskii
2003-03-18  2:10   ` Bob Rossi
2003-03-18  5:46     ` Eli Zaretskii
2003-02-10 22:28 Michael Elizabeth Chastain
2003-02-10 22:15 Bob Rossi
2003-02-11  6:39 ` Eli Zaretskii
2003-02-13  3:00   ` Bob Rossi

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=3E88A13D.6010405@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jason-swarelist@molenda.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