From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: vapier@gentoo.org
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: fix sparc memcpy fortify error
Date: Fri, 19 Mar 2010 09:26:00 -0000 [thread overview]
Message-ID: <201003190925.o2J9Pn8q004109@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <1268964549-30380-1-git-send-email-vapier@gentoo.org> (message from Mike Frysinger on Thu, 18 Mar 2010 22:09:09 -0400)
> From: Mike Frysinger <vapier@gentoo.org>
> Date: Thu, 18 Mar 2010 22:09:09 -0400
>
> Building on an x86_64-linux system with --enable-targets=all fails on the
> sparc code with a fortify error:
>
> cc1: warnings being treated as errors
> In file included from /usr/include/string.h:640,
> from gnulib/string.h:23,
> from ../../gdb/gdb_string.h:25,
> from ../../gdb/vec.h:25,
> from ../../gdb/memattr.h:24,
> from ../../gdb/target.h:60,
> from ../../gdb/exec.h:23,
> from ../../gdb/gdbcore.h:31,
> from ../../gdb/sparc-tdep.c:29:
> In function 'memcpy',
> inlined from 'sparc32_store_return_value' at ../../gdb/sparc-tdep.c:1112,
> inlined from 'sparc32_return_value' at ../../gdb/sparc-tdep.c:1170:
> /usr/include/bits/string3.h:52: error: call to __builtin___memcpy_chk will
> always overflow destination buffer
> make: *** [sparc-tdep.o] Error 1
That's a false positive I'm afraid. I agree that it isn't trivial to
see that there is no buffer overflow here. Unfortunately your
solution is a bit problematic:
> 2010-03-18 Mike Frysinger <vapier@gentoo.org>
>
> * gdb/sparc-tdep.c (sparc32_store_return_value): Declare the length
> of buf using the "len" variable.
>
> gdb/sparc-tdep.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/gdb/sparc-tdep.c b/gdb/sparc-tdep.c
> index f129a55..ea0cdd2 100644
> --- a/gdb/sparc-tdep.c
> +++ b/gdb/sparc-tdep.c
> @@ -1101,7 +1101,7 @@ sparc32_store_return_value (struct type *type, struct regcache *regcache,
> const gdb_byte *valbuf)
> {
> int len = TYPE_LENGTH (type);
> - gdb_byte buf[8];
> + gdb_byte buf[max(len, 8)];
Sorry, but variable sized arrays aren't C90.
Does it help if you replace
> gdb_assert (!(sparc_floating_p (type) && len == 16));
with
gdb_assert (len <= 8);
?
next prev parent reply other threads:[~2010-03-19 9:26 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
2010-03-19 8:42 ` Andreas Schwab
2010-03-19 17:10 ` Mike Frysinger
2010-03-19 9:26 ` Mark Kettenis [this message]
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=201003190925.o2J9Pn8q004109@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--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