Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Michal Ludvig <mludvig@suse.cz>
Cc: Michael Elizabeth Chastain <mec@shout.net>, gdb@sources.redhat.com
Subject: Re: GDB 5.1.92 available [patch]
Date: Mon, 29 Apr 2002 10:25:00 -0000	[thread overview]
Message-ID: <3CCD8209.4070407@cygnus.com> (raw)
In-Reply-To: <3CCD06C7.3040007@suse.cz>

> Michael Elizabeth Chastain wrote:
> The last-minute x86-64 warning has a typo in it:
> 
>   printf_filtered
>    ("NOTE: This function doesn't seem to have a valid prologue.\n"
>     "      Try to add -fno-omit-frame-pointer tou your gcc's CFLAGS.\n");
> 
> Thanks, fixed.
> 
> Index: x86-64-tdep.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/x86-64-tdep.c,v
> retrieving revision 1.9.2.2
> retrieving revision 1.9.2.3
> diff -u -r1.9.2.2 -r1.9.2.3
> --- x86-64-tdep.c       27 Apr 2002 00:11:18 -0000      1.9.2.2
> +++ x86-64-tdep.c       27 Apr 2002 22:57:23 -0000      1.9.2.3
> @@ -822,7 +822,7 @@
>    {
>      printf_filtered
>        ("NOTE: This function doesn't seem to have a valid prologue.\n"
> -       "      Try to add -fno-omit-frame-pointer tou your gcc's CFLAGS.\n");
> +       "      Consider adding -fno-omit-frame-pointer to your gcc's CFLAGS.\n");
>      omit_fp_note_printed++;
>    }
>   return pc;

Oops!  I should have been very clear that the 5.2 branch is frozen but I 
wasn't :-(.

Anyway, the change won't make it into 5.2.  That would mean re-building 
the tar-ball and that in turn would mean that people would again have to 
re-download and test it.

Andrew



  reply	other threads:[~2002-04-29 17:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-26 19:29 GDB 5.1.92 available Michael Elizabeth Chastain
2002-04-29  1:39 ` GDB 5.1.92 available [patch] Michal Ludvig
2002-04-29 10:25   ` Andrew Cagney [this message]
2002-04-29 11:17     ` Michal Ludvig
2002-04-29 11:46       ` Andrew Cagney

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=3CCD8209.4070407@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb@sources.redhat.com \
    --cc=mec@shout.net \
    --cc=mludvig@suse.cz \
    /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