This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: ASAN test failures make compare_tests useless


Hi!

On Mon, 18 Aug 2014 17:17:53 +0200, Manuel LÃpez-IbÃÃez <lopezibanez@gmail.com> wrote:
> On 18 August 2014 16:34, Alexander Potapenko <glider@google.com> wrote:
> > On Mon, Aug 18, 2014 at 9:43 AM, Yury Gribov <y.gribov@samsung.com> wrote:
> >> On 08/18/2014 09:42 AM, Yury Gribov wrote:
> >>>
> >>> On 08/16/2014 04:37 AM, Manuel LÃpez-IbÃÃez wrote:
> >>>>
> >>>> On the compile farm, ASAN tests seem to fail a lot like:
> >>>>
> >>>> FAIL: c-c++-common/asan/global-overflow-1.c   -O0  output pattern
> >>>> test, is ==31166==ERROR: AddressSanitizer failed to allocate
> >>>> 0xdfff0001000 (15392894357504) bytes at address 2008fff7000 (errno:
> >>>> 12)
> >>>> ==31166==ReserveShadowMemoryRange failed while trying to map
> >>>> 0xdfff0001000 bytes. Perhaps you're using ulimit -v
> >>>> , should match READ of size 1 at 0x[0-9a-f]+ thread T0.*(

I'm also annoyed by this, due to Âulimit -v 4194304Â being set.

> >>>> The problem is that those addresses and sizes are very random,
> > The output pattern that must be printed has these addresses masked out
> > (note "0x[0-9a-f]+" in your report).
> > No other lines with varying addresses should be printed.
> 
> For the record, I think the fault lies in the GCC testing
> infrastructure and not in ASAN. It is wrong to print as the test error
> message the output of ASAN. It should print
> 
> FAIL: c-c++-common/asan/global-overflow-1.c   -O0  output pattern
> test, is  ERROR
> 
> This is enough to see that something failed. For details one can go to
> the detailed logs. But I didn't add the asan testing infrastructure
> and I couldn't figure out how to fix this.
> 
> Any suggestions?

Richard Sandiford has already addressed this in DejaGnu upstream,
<http://news.gmane.org/find-root.php?message_id=%3C87bo0samke.fsf%40talisman.default%3E>,
so you now "just" need to wait for the next DejaGnu release to be made
and packaged for your distribution, or you manually patch
/usr/share/dejagnu/dg.exp:dg-test, or add a patched dg-test to a suitable
gcc/testsuite/lib/*.exp file to override the system one.


GrÃÃe,
 Thomas

Attachment: pgphM6AlO7gqa.pgp
Description: PGP signature


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]