From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 1AD7043F60 for ; Wed, 1 May 2024 14:19:29 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8AD50402A7; Wed, 1 May 2024 14:19:28 +0200 (CEST) Received: from mail-pl1-f177.google.com (mail-pl1-f177.google.com [209.85.214.177]) by mails.dpdk.org (Postfix) with ESMTP id CB1194021E for ; Wed, 1 May 2024 14:19:27 +0200 (CEST) Received: by mail-pl1-f177.google.com with SMTP id d9443c01a7336-1ec4dc64c6cso12451175ad.0 for ; Wed, 01 May 2024 05:19:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aviznetworks-com.20230601.gappssmtp.com; s=20230601; t=1714565966; x=1715170766; darn=dpdk.org; h=to:cc:date:message-id:subject:mime-version:from:from:to:cc:subject :date:message-id:reply-to; bh=Lv1LWgWFNKNoJ9qvofHY4HsUthhisP50GwX1AfRSbDc=; b=IhkQHztbhCtnqfI9JrLQVo3d1meGX7kBXnJ/X1UBOX+bbb+9OENwCO1H22BDGv1oU+ QvMZsyKsLukriR5LKK+7vkNks8UgZqQRE2u5hJBLiOG1fFuP146HMMgZKxxjfYzHBrdi kI/gWL/2Edj/Ab7gZOY6OtC7lzxvfS/PBBJx573p7892eyRZKffPaICId4yhsl/68ciE ekDwXABsY9X07s/QTzRZ8I6eT7yr6m4yDbgCDAzt4FbdkSFcTlALIqTouAae1aJmHAeV GN6/3sojnz9tKy/ozjSczI2syWCs5L2CENgHWOZs8lrNFpKzNcu2nAGfmG5c4vlw6rEq HhsQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714565966; x=1715170766; h=to:cc:date:message-id:subject:mime-version:from:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Lv1LWgWFNKNoJ9qvofHY4HsUthhisP50GwX1AfRSbDc=; b=HJxAZaC1wEgTCW5qVgp6rE/fQVzzqmdclUxgjlvbvNMFuupqZnLVUQJrW8cP9bC6kj 7oBPxyah8UHx0INbBZM/9yMqvrQhqBqkl3tDoPIl8AryD1/j2wFjcw1r4vEyNei3ipMc sC/ry6F/ExjcbdRAOM77Fcfq1VUaeZFQIq2Cu7KiKLFI5xrwIrlatHwlmE29wQP5+qbS sa+ATg4aBz14eI+J/EN6zhcB7c7CIm+LnRXSLYXPIOdfYaIvS/rBRWJgypGZyUuAozn8 x/3jAxphwlBt/fOu9KAoTMPxaHua1RWJup8ILbdjQ4aWdHx0IzL+kwnAtFMrGlbIGJqy cC2w== X-Gm-Message-State: AOJu0YyRr6UZ3orFzW3eyKKUOP7PDHlgQEPc/T64RRe+CyhdUubu0dNW QVXlx5EsILkbqPGjYL2WOPELMO6uRyfhR1SCH5laRwZxQjyVZ91bVjgDSfUsFqlLf4Qo83crGRz o X-Google-Smtp-Source: AGHT+IEXL6zV09MvLq4ehwDqAhJ+2NCxx8GXbgHN1JaKKzVqf0RfFjsElhEmBAs4q1ZAdj0pgbJrXg== X-Received: by 2002:a17:902:e88d:b0:1e4:3ed8:e264 with SMTP id w13-20020a170902e88d00b001e43ed8e264mr3327416plg.43.1714565966290; Wed, 01 May 2024 05:19:26 -0700 (PDT) Received: from smtpclient.apple ([2409:40f4:1113:4cee:e4fb:76fd:7270:8eac]) by smtp.gmail.com with ESMTPSA id i16-20020a17090332d000b001e0c568ae8fsm23959760plr.192.2024.05.01.05.19.24 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 May 2024 05:19:25 -0700 (PDT) From: Harrish SJ Content-Type: multipart/alternative; boundary="Apple-Mail=_F21E5E84-49B2-46E9-AB8C-C9867D174886" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\)) Subject: Reg the Valgrind support for DPDK App Message-Id: Date: Wed, 1 May 2024 17:49:12 +0530 Cc: IIanChezhian Raman , Jatin Batra To: users@dpdk.org X-Mailer: Apple Mail (2.3774.500.171.1.1) X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org --Apple-Mail=_F21E5E84-49B2-46E9-AB8C-C9867D174886 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi DPDK Community, We are trying to attach Valgrind to DPDK testpmd/helloworld APP but = observing that the initialization is stuck for longer time in = rte_eal_memory_init() =E2=80=94> rte_eal_memseg_init() =E2=80=94> = memseg_primary_init() =E2=80=94> eal_dynmem_memseg_lists_init() =E2=80=94>= eal_memseg_list_alloc() API with below logs: =3D=3D997317=3D=3D Warning: set address range perms: large range = [0x1405800000, 0x1805a00000) (noaccess) =3D=3D997317=3D=3D Warning: set address range perms: large range = [0x1405800000, 0x1805a00000) (noaccess) =3D=3D997317=3D=3D Warning: set address range perms: large range = [0x1405800000, 0x1805a00000) (noaccess) We have tried with both standard Valgrind and = https://github.com/bluca/valgrind-dpdk as well. Could you please help us with the steps and procedure to run Valgrind = for DPDK APP or any other procedures to find memleak in the code.? Thanks in advance, Regards and Thanks, Harrish.S.J --Apple-Mail=_F21E5E84-49B2-46E9-AB8C-C9867D174886 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Hi DPDK = Community,

We are trying to attach Valgrind to DPDK = testpmd/helloworld APP but observing that the initialization is stuck = for longer time in rte_eal_memory_init() =E2=80=94> = rte_eal_memseg_init() =E2=80=94> memseg_primary_init() =E2=80=94> = eal_dynmem_memseg_lists_init() =E2=80=94> eal_memseg_list_alloc() = API with below logs:

=3D=3D997317=3D=3D = Warning: set address range perms: large range [0x1405800000, = 0x1805a00000) (noaccess)
=3D=3D997317=3D=3D Warning: set = address range perms: large range [0x1405800000, 0x1805a00000) = (noaccess)
=3D=3D997317=3D=3D Warning: set address range = perms: large range [0x1405800000, 0x1805a00000) = (noaccess)

We have tried with both = standard Valgrind and https://github.com/bluca/v= algrind-dpdk as well.
Could you please help us with = the steps and procedure to run Valgrind for DPDK APP or any other = procedures to find memleak in the code.?
Thanks in = advance,

Regards and = Thanks,
Harrish.S.J

= --Apple-Mail=_F21E5E84-49B2-46E9-AB8C-C9867D174886--