Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew STUBBS <andrew.stubbs@st.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFC] Move the frame zero PC check earlier
Date: Fri, 21 Jul 2006 15:52:00 -0000	[thread overview]
Message-ID: <44C0F828.4090807@st.com> (raw)
In-Reply-To: <20060521020434.GA9432@nevyn.them.org>

Did anything more happen to this since May?

This is a feature I would like to see.

Daniel Jacobowitz wrote:
> On Sat, May 20, 2006 at 11:29:04PM +0200, Mark Kettenis wrote:
>> I actually think that something like that is the way to go.  It's
>> closely related to what Dan wrote about in:
>>
>> http://sourceware.org/ml/gdb/2006-05/msg00109.html
>>
>> and I'd like to have a go at implementing option #2 in that mail.
> 
> That (the frame unwinder end-of-stack method) wouldn't actually help
> with this problem; that's why I sent the two separately (they were
> originally the same message when I was writing it).  The architecture
> unwinder could report a saved pc of zero as terminating the stack, but
> in all the cases I'm interested in, the DWARF-2 unwinder is actually
> used for the bottom frame.
> 
>> Unfortunately I'm leaving for a a four-week trip tomorrow.  I won't be
>> able to read my mail for most of the time between now and june 17.
> 
> Well, enjoy your trip.  I have a thousand different things that need
> merging, and I'll be working on them over the coming weeks; but it
> won't do me any harm to table this one until we have time to discuss it
> further, as long as we've deliberately postponed it rather than let it
> fall through :-)
> 
> So, I shall not pursue this patch right now, and we'll discuss it later
> (probably not until July; the GCC Summit at the end of June is going to
> wreck my schedule around when you get back).  Thanks for all the
> comments!
> 


  reply	other threads:[~2006-07-21 15:52 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-10 18:03 Daniel Jacobowitz
2006-05-11 10:42 ` Andrew STUBBS
2006-05-11 22:24 ` Jim Blandy
2006-05-11 22:32   ` Daniel Jacobowitz
2006-05-12  6:21     ` Jim Blandy
2006-05-12 12:46       ` Daniel Jacobowitz
2006-05-13 10:14 ` Mark Kettenis
2006-05-13 15:17   ` Daniel Jacobowitz
2006-05-13 15:46     ` Daniel Jacobowitz
2006-05-13 17:08       ` Mark Kettenis
2006-05-13 16:49     ` Mark Kettenis
2006-05-13 18:53       ` Daniel Jacobowitz
2006-05-16 21:38       ` Daniel Jacobowitz
2006-05-16 22:19         ` Mark Kettenis
2006-05-16 22:46           ` Daniel Jacobowitz
2006-05-16 23:53             ` PAUL GILLIAM
2006-05-18  1:35               ` Joel Brobecker
2006-05-18  9:31                 ` Jim Blandy
2006-05-18 10:09                   ` Andrew STUBBS
2006-05-18 17:36                     ` Jim Blandy
2006-05-18 18:09                       ` PAUL GILLIAM
2006-05-18 20:04                         ` Jim Blandy
2006-05-18 20:43                           ` Mark Kettenis
2006-05-18 23:31                             ` Jim Blandy
2006-05-20 22:26                               ` Mark Kettenis
2006-05-21  2:12                                 ` Daniel Jacobowitz
2006-07-21 15:52                                   ` Andrew STUBBS [this message]
2006-07-22 11:23                                     ` Mark Kettenis
2006-07-24 19:32                                       ` Daniel Jacobowitz
2006-07-26 22:16                                         ` Mark Kettenis
2006-07-26 22:25                                           ` Daniel Jacobowitz
2006-05-19  3:32                             ` Daniel Jacobowitz
2006-05-20 21:30                               ` Mark Kettenis
2006-05-19 12:26                             ` Eli Zaretskii
2006-05-19 18:12                               ` Jim Blandy
2006-05-19 18:53                                 ` Eli Zaretskii
2006-05-22 23:15                                   ` Jim Blandy
2006-05-15 13:57   ` Andrew STUBBS

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=44C0F828.4090807@st.com \
    --to=andrew.stubbs@st.com \
    --cc=gdb-patches@sourceware.org \
    /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