Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: davidm@hpl.hp.com, gdb@sources.redhat.com
Subject: Re: question on gdbarch_skip_prologue()
Date: Thu, 07 Mar 2002 11:55:00 -0000	[thread overview]
Message-ID: <15495.50576.881175.462946@napali.hpl.hp.com> (raw)
In-Reply-To: <1020307184128.ZM28576@localhost.localdomain>

>>>>> On Thu, 7 Mar 2002 11:41:28 -0700, Kevin Buettner <kevinb@redhat.com> said:

  Kevin> But you should also know that most (all?) of us working on
  Kevin> GDB don't really like this behavior and are eagerly waiting
  Kevin> for the day when it'll be possible to implement
  Kevin> skip_prologue() as the identity function (on the first
  Kevin> argument).

Ah, I'm happy to hear that.

OK, here is my take then: longer term, skip_prologue() should become
an identity function.  In the interim, we can continue to use
code-reading based heuristics and debug info to implement it.  The
important point for me is that the routine does not need any special
support from the unwind library.

Of course, this implies that, for the moment, we can't get rid of
code-reading entirely in gdb/ia64, but longer term, we will be able to
do so.

	--david


      reply	other threads:[~2002-03-07 19:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-06 22:28 David Mosberger
     [not found] ` <davidm@napali.hpl.hp.com>
2002-03-07  0:12   ` Kevin Buettner
2002-03-07 10:13     ` David Mosberger
2002-03-07 10:42   ` Kevin Buettner
2002-03-07 11:55     ` David Mosberger [this message]

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=15495.50576.881175.462946@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=davidm@hpl.hp.com \
    --cc=gdb@sources.redhat.com \
    --cc=kevinb@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