From: Florian Weimer <fweimer@redhat.com>
To: William Brana <wbrana@gmail.com>, gcc-help@gcc.gnu.org
Subject: Re: libXcursor + -finline-functions: Invalid read of size 4
Date: Mon, 11 Aug 2014 08:43:00 -0000 [thread overview]
Message-ID: <53E8822F.3010100@redhat.com> (raw)
In-Reply-To: <CAJ7jCmkE3sL95GHe+VruBk9EN7qBfTSFAa_t2dc=0H0w=kwGDw@mail.gmail.com>
On 08/08/2014 01:15 PM, William Brana wrote:
> Hello,
> I'm getting warnings like following from valgrind when libXcursor is
> compiled with -O2 -finline-functions and gcc 4.8.3 or 4.7.4, but not
> with -O2.
> Is it miscompiled or false positive?
Can you run valgrind with debugging information? It might us tell us at
least which allocation is too short.
It could be a harmless over-read from the libc string functions
(particularly if valgrind has not been set up correctly on your system).
--
Florian Weimer / Red Hat Product Security
next prev parent reply other threads:[~2014-08-11 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 11:15 William Brana
2014-08-11 8:43 ` Florian Weimer [this message]
2014-08-12 14:57 ` William Brana
2014-08-12 15:17 ` Florian Weimer
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=53E8822F.3010100@redhat.com \
--to=fweimer@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=wbrana@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).