From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ua0-f170.google.com (mail-ua0-f170.google.com [209.85.217.170]) by dpdk.org (Postfix) with ESMTP id 705022934 for ; Fri, 4 Nov 2016 02:45:54 +0100 (CET) Received: by mail-ua0-f170.google.com with SMTP id 20so55028822uak.0 for ; Thu, 03 Nov 2016 18:45:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=F8pHkO/nD69v3ZMkpX7Ck4I6NrNlevYY7H1QfS01G0A=; b=g02VpOCw8gWbxOP3eUdW3ms4yO9v0yjnBnfOCQyNsHw5ru0LlHBjNUqvfSvQVhnqaH 4j1/lhcIj4Z9PPbOFS5qTlImiPOokGpJgEcII6SvI8M3BHcYSZDjHVrgtEHAXV/qpUjy wkPYqx4VdhVHfTfCQ/cFP5WnFB2rylcyQiFBz+q0oF15G8osB3V+c0yVXft/FsHwego+ XBWYqNwBxtnqrvx4oLdv8rKW2nHktjqIv2bRZt0/FMfYgMX3q3Jrv/IvhhRgKaw37a7I B+Ci4nIehFvutvxEQw1MMhXRDPUGnh4u4i/T9/z6HLxrpB3/K1ESyRSbjxTH/aRYCJ7t mB+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=F8pHkO/nD69v3ZMkpX7Ck4I6NrNlevYY7H1QfS01G0A=; b=D5j9lWaXS09XjRMxzsRdBqZj8Q6Ht//+d+tVA7M12mLpjqF1LhrxIzen0SsJPV/KiX 5mN5ybcEsYadpsx3S5d4uQ0rmZAghxu3VbxiJs/Ok3mmag6Kaaqmp/eKDtptGuQcH1LX mxSPwPIkXdox2BDyxJJdNV2SjvYTZcUDCGJ5gnUd0IoLaWqyor6eGj2WaVsMUZRD1Fx0 OkQQc+2Uv5PgGNQtpQenlpMxswl0IFwEM2DLH9WcdsRn3ZRebp+wzpRm/GXTpISEPsJr jlSWvcfm+DbDsjUs+5ULf8JvZOMAtx6hUUQs9VsDXWypgTSZMgoBtcGTUg8ba9r4GNQH 4gsw== X-Gm-Message-State: ABUngvdVuMe4+n9aDJYWIkaAkojJ/RenFuu3C2BAVqeubmR4p7AbQIy5sZ6wBEf54CZ1sljE3qD21Qy0b6mcwQ== X-Received: by 10.159.48.145 with SMTP id j17mr8174187uab.43.1478223953829; Thu, 03 Nov 2016 18:45:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.37.199 with HTTP; Thu, 3 Nov 2016 18:45:53 -0700 (PDT) In-Reply-To: References: From: Sruthi Yellamraju Date: Thu, 3 Nov 2016 21:45:53 -0400 Message-ID: To: XIAO Xiaohong , users@dpdk.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] DPDK-16.07: segfault when calling rte_eth_stats_get() from secondary process X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2016 01:45:54 -0000 Both primary and secondary processes are built and running off 16.07 On Thursday, November 3, 2016, XIAO Xiaohong < Xiaohong.Xiao@alcatel-sbell.com.cn> wrote: > Hello > You said your primary process calls a shared library, then what's the DPD= K > version this shared library is built on? > Can you make sure the primary and secondary process both are using same > DPDK version? > > -----Original Message----- > From: users [mailto:users-bounces@dpdk.org ] On Behalf Of > Sruthi Yellamraju > Sent: 2016=E5=B9=B411=E6=9C=884=E6=97=A5 6:49 > To: users@dpdk.org > Subject: [dpdk-users] DPDK-16.07: segfault when calling > rte_eth_stats_get() from secondary process > > Hi, > > I am using DPDK 16.07 with fm10k. I am seeing segfaults when calling > rte_eth_stats_get() API from a secondary process. > > The primary process doesnt call DPDK APIs directly and hence doesnt link > against DPDK Libraries. The primary process uses a shared library that in > turn is using DPDK APIs and links with DPDK libraries. All DPDK libraries > are built as static libraries. > > The secondary process uses DPDK APIs directly and hence links against the > DPDK static libraries directly. > > When i run the secondary process to get stats (something like > dpdk-procinfo) application, it segfaults (Error 14). gdb shows: > (gdb) bt > #0 0x00007fffeacd72bc in ?? () --> points to stats API offset in the > primary processes' shared library > #1 0x00000000006761d7 in fm10k_update_hw_stats () > #2 0x0000000000650dee in fm10k_stats_get () > #3 0x000000000043803d in rte_eth_stats_get () > #4 0x0000000000a68663 in do_get_stats (argc=3D, > argv=3D0x7fffffffe478) at dpdk_status.c:225 > #5 main (argc=3D, argv=3D0x7fffffffe478) at > dpdk_status.c:501 > > Any clues on why this could be happening? I am guessing this needs some > linker magic to get it to work. Not sure what exactly. I played with a > couple of options , but in vain. > > Any pointers will be greatly appreciated. > > Thanks! >