DPDK usage discussions
 help / color / mirror / Atom feed
From: Sruthi Yellamraju <ysruthi@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] DPDK-16.07: segfault when calling rte_eth_stats_get() from secondary process
Date: Thu, 3 Nov 2016 18:48:54 -0400	[thread overview]
Message-ID: <CAFxVZ5KSYqfXj4i3cyscTw+wV87Zcsk5G0mKXKNCHaeGqEoPkw@mail.gmail.com> (raw)

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=<value optimized out>,
argv=0x7fffffffe478) at dpdk_status.c:225
#5  main (argc=<value optimized out>, argv=0x7fffffffe478) 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!

             reply	other threads:[~2016-11-03 22:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-03 22:48 Sruthi Yellamraju [this message]
     [not found] ` <B7D7F8603F786C4995D904365BDCCDAD1F0547BC@cnshjmbx03>
2016-11-04  1:45   ` Sruthi Yellamraju
2016-11-04  3:41     ` Sruthi Yellamraju

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFxVZ5KSYqfXj4i3cyscTw+wV87Zcsk5G0mKXKNCHaeGqEoPkw@mail.gmail.com \
    --to=ysruthi@gmail.com \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).