From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f178.google.com (mail-pf0-f178.google.com [209.85.192.178]) by dpdk.org (Postfix) with ESMTP id 5FEC71B3BF for ; Tue, 3 Oct 2017 17:49:28 +0200 (CEST) Received: by mail-pf0-f178.google.com with SMTP id u12so4784421pfl.4 for ; Tue, 03 Oct 2017 08:49:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=BHXX7Jhl6pDwwChcWZrDuvfBs9BAff7swQe4w76VKeM=; b=hClYvnVX9HmPFwjOQizHA1w/22hdRMnCwnheuFML4qiMYA0PIlJKtmWT3vUQy6AkNl CG2P8aC3Dtlg30+aGiCsoIC86/uv8TD1YlJTgjvSjn2eIouIRyo99GIIuWHEgwpZfJ2W JkD38lu7+ZqWDN9akaXgkjt/oY+BLhKvkheKv8wtbPqyTU0tQiU0VvlBuSkekB4v6tx0 bti1j32pdwyeoW+K9AzPGGlHuFP94rP0b8pzF+3FdbMqN8dusjftVoX/Oidcs0pHCUEi h/c5ceBspLFgu/L4B54EmdekCPZSFnf7rFq85BV0A6RhETPJFXdjAKWBZHZAkoCVL+Bs mJDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=BHXX7Jhl6pDwwChcWZrDuvfBs9BAff7swQe4w76VKeM=; b=Ir+ry8dGi5uf1Mzj4/Y3ET8AYpFzKsjDQd6HBw1RrRb269EPuT62sAh3o8Fgly2gHi tO9yJYZ3Y1dBfrApqYPkbAIrswGqUX0yjlNUFqNFPEbIJCn+DLouvD8PUoRohx9mYZUA k81jIWNin8BtRWEFU3tVgyjNbvyyaBhtG+m3EHi+caabygtF5U35b9mT/7PQAjxWKQcH VSlv6/ZISPurwMq2LFoux//Bt01OUNYtFyxVpBN04dVataPTcq7pFONaWHmZRAk8Neft wXbfDo8MvKKl807qQcWDlINQD7KsQ3r9AkaVDzIntW0+2x8TRvH6rbQ7p8lbyXBH6DQG 9S7w== X-Gm-Message-State: AHPjjUh6SH8y63819dmaM6/d1dzJsNdJlJMV4FPNz51XwDZoAJ0pJA5E wO6wvDSaGRBBoFfyLzVtJALKX4zQ3FA= X-Google-Smtp-Source: AOwi7QAZ50vz7D2zQuhFdeAtx1TLT0EItqsyFjZNxJ4x96IMIAEupUcDEIc5+uEtiG7VTsEfdLU6Hw== X-Received: by 10.98.10.146 with SMTP id 18mr17396908pfk.346.1507045767568; Tue, 03 Oct 2017 08:49:27 -0700 (PDT) Received: from xeon-e3 (76-14-207-240.or.wavecable.com. [76.14.207.240]) by smtp.gmail.com with ESMTPSA id y5sm23755559pfd.89.2017.10.03.08.49.27 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 03 Oct 2017 08:49:27 -0700 (PDT) Date: Tue, 3 Oct 2017 08:49:19 -0700 From: Stephen Hemminger To: Kumaraparameshwaran Rathnavel Cc: users@dpdk.org Message-ID: <20171003084919.5ee9a3a7@xeon-e3> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-users] DPDK Memory in GDB X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 15:49:28 -0000 On Tue, 3 Oct 2017 15:11:32 +0530 Kumaraparameshwaran Rathnavel wrote: > Hi All, > > We have been using the mempool of the DPDK for our application. Whenever there is a core dump and if I try to print the contents of the pointer allocated from rte_malloc gdb is throwing an error saying cannot access the memory at address. During run time this is working fine . This happens only when examining a core. I replaced rte_mallloc with malloc and in this case I am able to print the contents of the pointer. I have built DPDK with -g option. Am I doing anything wrong here? > > Thanking You, > Param. That is probably intentional. Core dumps don't dump huge page memory (to save space). A 16G core file would not work well. Also hugepages are shared between multiple processes.