Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: ac131313@cygnus.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Kill SKIP_PROLOGUE_FRAMELESS_P
Date: Sun, 21 Apr 2002 18:40:00 -0000	[thread overview]
Message-ID: <20020421.183114.00007851.davem@redhat.com> (raw)
In-Reply-To: <3CC368A4.6050601@cygnus.com>

   From: Andrew Cagney <ac131313@cygnus.com>
   Date: Sun, 21 Apr 2002 21:34:28 -0400

   Can you also please remember to create patches against current sources. 
     That way everyones life is easier (and in this case I could have 
   reviewed it a lot quicker).
   
Ok.

   Anyway, can you please update the documentation (obvious) - it now 
   refers to a non-existant macro.
   
Done, thusly.

2002-04-21  David S. Miller  <davem@redhat.com>

	* gdbint.texinfo (SKIP_PROLOGUE_FRAMELESS_P): Delete definition.

--- gdbint.texinfo.~1~	Sun Apr 21 08:52:35 2002
+++ gdbint.texinfo	Sun Apr 21 18:35:29 2002
@@ -3415,12 +3415,6 @@
 A C expression that returns the address of the ``real'' code beyond the
 function entry prologue found at @var{pc}.
 
-@item SKIP_PROLOGUE_FRAMELESS_P
-@findex SKIP_PROLOGUE_FRAMELESS_P
-A C expression that should behave similarly, but that can stop as soon
-as the function is known to have a frame.  If not defined,
-@code{SKIP_PROLOGUE} will be used instead.
-
 @item SKIP_TRAMPOLINE_CODE (@var{pc})
 @findex SKIP_TRAMPOLINE_CODE
 If the target machine has trampoline code that sits between callers and

   


      reply	other threads:[~2002-04-22  1:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-21  2:16 David S. Miller
2002-04-21 11:40 ` Andrew Cagney
2002-04-21 17:27   ` David S. Miller
2002-04-21 17:51   ` David S. Miller
2002-04-21 18:34     ` Andrew Cagney
2002-04-21 18:40       ` David S. Miller [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=20020421.183114.00007851.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.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