From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 34E9AA0530 for ; Wed, 22 Jan 2020 11:52:35 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 1BB592B8B; Wed, 22 Jan 2020 11:52:34 +0100 (CET) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 00DD2E07; Wed, 22 Jan 2020 11:52:31 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Jan 2020 02:52:29 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.70,349,1574150400"; d="scan'208";a="425815193" Received: from aburakov-mobl.ger.corp.intel.com (HELO [10.237.220.124]) ([10.237.220.124]) by fmsmga005.fm.intel.com with ESMTP; 22 Jan 2020 02:52:28 -0800 To: Lalithaditya Naidu Gajula , users@dpdk.org, dev@dpdk.org References: From: "Burakov, Anatoly" Message-ID: <4cd99005-1777-0abd-caf9-ce2a46a5d45e@intel.com> Date: Wed, 22 Jan 2020 10:52:28 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-users] [dpdk-dev] Issue :- segmentation fault in rte_eal_wait_lcore. 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: , Errors-To: users-bounces@dpdk.org Sender: "users" On 20-Jan-20 7:34 AM, Lalithaditya Naidu Gajula wrote: > Hi All, > I got a segmentation fault issue regarding ret_eal_wait_lcore and > rte_eal_mp_wait_lcore(), > when i am running the code in a few logical cores using rte_eal_remote > _launch() function which has a while (1) (infinite loop) in all the > functions launched by remote launch and when i am terminating the code with > 'ctrl+c' i am getting segmentation fault at rte_eal_mp_wait_lcore(), then > I replaced that with rte_eal_wait_lcore() for the respective logical cores > even then i am getting a segmentation fault, can anyone please clarify this > issue? > It sounds like you have memory corruption somewhere in your code. Have you tried looking at it in gdb and stepping through your code to see if you get any wrong memory accesses? -- Thanks, Anatoly