Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] segfault in StarPU memory allocator

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] segfault in StarPU memory allocator


Chronologique Discussions 
    < Chronologique >      < Discussions >
  • From: Samuel Thibault <samuel.thibault@inria.fr>
  • To: Alfredo Buttari <alfredo.buttari@enseeiht.fr>
  • Cc: starpu-devel@lists.gforge.inria.fr
  • Subject: Re: [Starpu-devel] segfault in StarPU memory allocator
  • Date: Mon, 2 Jul 2018 23:20:27 +0200
  • Authentication-results: mail2-smtp-roc.national.inria.fr; spf=None smtp.pra=samuel.thibault@inria.fr; spf=Neutral smtp.mailfrom=samuel.thibault@ens-lyon.org; spf=Pass smtp.helo=postmaster@hera.aquilenet.fr
  • Ironport-phdr: 9a23:/qg1BhwaPUWlzoDXCy+O+j09IxM/srCxBDY+r6Qd2ugXIJqq85mqBkHD//Il1AaPAd2Fraocw8Pt8InYEVQa5piAtH1QOLdtbDQizfssogo7HcSeAlf6JvO5JwYzHcBFSUM3tyrjaRsdF8nxfUDdrWOv5jAOBBr/KRB1JuPoEYLOksi7ze+/94HSbglSmDaxfa55IQmrownWqsQYm5ZpJLwryhvOrHtIeuBWyn1tKFmOgRvy5dq+8YB6/ShItP0v68BPUaPhf6QlVrNYFygpM3o05MLwqxbOSxaE62YGXWUXlhpIBBXF7A3/U5zsvCb2qvZx1S+HNsDtU7s6RSqt4LtqSB/wiScIKTg58H3MisdtiK5XuQ+tqwBjz4LRZoyeKfhwcb7Hfd4CS2RPXthfWTFCDIOyYIQAE/cOMuRfr4bzvFYOsQeyCRWwCO/z0DJEmHn71rA63eQ7FgHG2RQtEc8Uv3TRsdX6KqMSWv2rwqnIzDXMdOlZ2Sr56IjUbxsspuqMUqh1ccrM10YvExnJjkmQqYzkJDyazPkNs2yH7+d7VOKvjXQnqwBrrTS1yMcskJDEi4QIwV7K8iV5xZw6Jdy+SENjfNKpEoFctzqdN4ZwX8gsQHlotT4nxrAFuZO3ZjYGxZopyhLFdvCLb5SE7gj+WOqJPzt3nm5pdK+6ihms/0WtyujxWteq31pXsyZIl8XDum4N2hDP78WKRPpw8lu/1TuK1A3e6+9EIU4xmKrVNZEt3KI/m58SvEvZAyP7nEP7h7KMeEo+4Oin8eHnb63mppCCM490jRnzMqQwlcylG+s0KBIBX3GG+eS90L3s40v5T6tWjvEsnKnZqojWJcUdpqGnHw9Yypsv5hW/Aju8ztgVk3cKIEhYdB6bk4TlIUzCLOj9DfilglSslDlrx+rBPr3kGpjNNWLMkLL8fblj705Q0hYzzdBe551PEL4BPfbzWlPqudPGCB85KBW4w+LnCdV60IMSQ2WPArWWMK/Kq1+H+vovI/WQZI8SoDv9MOQl6OT0jX8hhF8RZLSm0oUJaH+mGvRrOEGZYXv3gtcdCmcGpAU+TOLtiF2YXj5ceWy+X6M65jEhCYKpF53PRo63gO/J4CDuN5lYfG1KDRimDGv0fp+FE6MFbCyIL8Nm1DYZSaSoUY4J2Be1uQL7y6YhIPCCqQMCspe279Fw+uDX3S0y9DZ9EsCBmzWWRmRpk2dOWz831qlipVBVy1GZ0KE+jeYORo8b3O9ATgpvbc2U9Od9Ed2nH1uZJo7YGmbjec2vBHQKdvx0xtYPZ0hnHND70kLO2THvB64SkfqMHpNmqPuAjUi0HN50zjP97Idkl0MvG5MdNGu8h6c5+RKBX9eUwXXcrL6jcOEn5ACI9GqHyjPf7kFVSgc2WLzYXHQSYEbK69rjtBrP
  • List-archive: <http://lists.gforge.inria.fr/pipermail/starpu-devel/>
  • List-id: "Developers list. For discussion of new features, code changes, etc." <starpu-devel.lists.gforge.inria.fr>
  • Organization: I am not organized
Alfredo Buttari, le lun. 02 juil. 2018 16:57:27 +0200, a ecrit:
> Unfortunately valgrind does not like CUDA code:
>
> ==1292== Memcheck, a memory error detector
> ==1292== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
> ==1292== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
> ==1292== Command: ./dqrm_test
> ==1292==
> vex amd64->IR: unhandled instruction bytes: 0xF 0xAE 0x64 0x24 0x40
> 0x48 0x8B 0x73
> vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
> vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=0F
> vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
> ==1292== valgrind: Unrecognised instruction at address 0x4015f48.
> ==1292== at 0x4015F48: _dl_runtime_resolve_xsave (in
> /usr/lib64/ld-2.17.so)
> [cut]

Mmm, it's not CUDA that it doesn't like, but the glibc itself. Valgrind
3.10 is indeed quite old, you need to upgrade it to get it to work with
recent glibc.

Samuel


Archives gérées par MHonArc 2.6.19+.

Haut de le page