Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: fix sparc memcpy fortify error
Date: Fri, 19 Mar 2010 08:18:00 -0000	[thread overview]
Message-ID: <daef60381003190118r18ce9f51v787b1f3f04c15f64@mail.gmail.com> (raw)
In-Reply-To: <83ocikiwm6.fsf@gnu.org>

Hi,

I got this issue in a amd64 ubuntu 9.04.
I reported it before, someone tell me that this is the bug of gcc.

Now, I handle this issue in this pc is  remove all the sparc function
from init.c file.

Thanks,
Hui

On Fri, Mar 19, 2010 at 15:44, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Mike Frysinger <vapier@gentoo.org>
>> Date: Thu, 18 Mar 2010 22:09:09 -0400
>>
>> -  gdb_byte buf[8];
>> +  gdb_byte buf[max(len, 8)];
>
> Isn't this Standard C only under C9x?  If so, we don't yet require
> that standard version, AFAIK.
>


  reply	other threads:[~2010-03-19  8:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19  2:09 Mike Frysinger
2010-03-19  7:45 ` Eli Zaretskii
2010-03-19  8:18   ` Hui Zhu [this message]
2010-03-19  8:42     ` Andreas Schwab
2010-03-19 17:10     ` Mike Frysinger
2010-03-19  9:26 ` Mark Kettenis
2010-03-19 17:09   ` Mike Frysinger
2010-03-19 20:11 ` [PATCH] gdb: workaround " Mike Frysinger
2010-04-19 18:59   ` Mike Frysinger
2010-04-21 15:30     ` Joel Brobecker
2010-04-21 15:38       ` Tom Tromey
2010-04-21 16:01         ` Joel Brobecker
2010-04-21 16:10           ` Mark Kettenis
2010-04-21 19:40             ` Mike Frysinger
2010-04-21 19:56               ` Mark Kettenis
2010-04-21 20:12                 ` Mike Frysinger

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=daef60381003190118r18ce9f51v787b1f3f04c15f64@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=vapier@gentoo.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