From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f169.google.com (mail-pf0-f169.google.com [209.85.192.169]) by dpdk.org (Postfix) with ESMTP id 3C8D61B30C for ; Tue, 3 Oct 2017 11:41:39 +0200 (CEST) Received: by mail-pf0-f169.google.com with SMTP id a1so1071363pfj.9 for ; Tue, 03 Oct 2017 02:41:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudsimple-com.20150623.gappssmtp.com; s=20150623; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=sBGTIij0lL+nA2nzKaoJxwqVYheCbWTv82dPs46uxzY=; b=ma9MNPOFSKTOXjOmHhinKRIs8tB22MDkLoIHwwB7CDLCO/FkGV0N/oc6nFd95tRKlg gno9lp34mDwpCiEREnWGzDWYi0dPgRzIK3GP+kJqm1dZDpZB8YikITtuaIQHAcNUWNGt Dk8d+gKpPI08AyczUwhofGjwZvIh4pLXL2ccQTZYdXeGMYWS8QAlk7/fF/CkhLXOYRSN YceIbI3Rso+oPlePoU+ng/1wcGDltIsm2+Cql95Zmy94Y4ZlFqR08m/IDyNp00jSFy4u lJHq+IdfN9XISB63T5fsnymQ2JkbSnMwfEpEc/ee0JPe+JcGQ83UqkyJc/L70MwHCtlI 4b6g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=sBGTIij0lL+nA2nzKaoJxwqVYheCbWTv82dPs46uxzY=; b=h89Z/OmRgc+sUXudPFKpUf5fu0UkamiaVrPkl6xPY0iJqkd2SdQqHu3ZtP6oleUU3E h4r+H8uCosH8muF2OXXCNd2u5dtOVwdkfjvOYg7bQruGlos+zKwJAEiAR2JACu7DYGrT +XUhCYsTEAZna6LIO22NOp/y88iIGTyOrwcaGUrVZJO0zbUBLzXQWaLlAcGajasTACmL 7hU2b1KcUg4lJXWt67mo1V/pdrAa/Dv0hoiS9Gu8HnXzatjankma97WCkoTLUwX1zXDW IDYDsf9/TeqxmqsmsjNxIJHHfAswlFFCNZzGUaF+H+4+bi8U+4Tm7l1t9lKEHR4+t/9w WtQQ== X-Gm-Message-State: AMCzsaVR8Sm6c8TAHZg6yDc5hwLr0q3v87HBgo+qUOz0J7RMQ+u8kh/K 0Qcm00XbSnWjQ3TdLeftUMiu6L83jHhBT67DT++ZmpCk220Zd2DGnpvqY2wO3AzCrsuzZ8hT1GX q1EGcgw+okZQpoT49zZlfEQEIAywdweSK864Ab0HSZ/SoDr4KdfztQQthiWg= X-Google-Smtp-Source: AOwi7QDnx4xUuSnx0kaE+JcJd7lozuZIjlKgqDX2hkyMaZeJCIj+D0CLBvmgs3aBxuyISOVPBWLFjA== X-Received: by 10.99.124.88 with SMTP id l24mr798881pgn.397.1507023697820; Tue, 03 Oct 2017 02:41:37 -0700 (PDT) Received: from [192.168.2.24] ([106.51.65.217]) by smtp.gmail.com with ESMTPSA id n10sm20662697pfh.121.2017.10.03.02.41.35 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Oct 2017 02:41:36 -0700 (PDT) From: Kumaraparameshwaran Rathnavel Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Message-Id: Date: Tue, 3 Oct 2017 15:11:32 +0530 To: users@dpdk.org X-Mailer: Apple Mail (2.3273) Subject: [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 09:41:39 -0000 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.=