From: Caianning <caianning@huawei.com>
To: "users@dpdk.org" <users@dpdk.org>
Cc: Houzhipeng <houzhipeng@huawei.com>, "Hu, Xuekun" <xuekun.hu@intel.com>
Subject: [dpdk-users] Is this a bug?//Re: pktgen segment fault when running save cmd
Date: Wed, 14 Sep 2016 06:34:40 +0000 [thread overview]
Message-ID: <F994AE62EFA2864BAC5A2B81D86C27C13E2D4F23@nkgeml514-mbx.china.huawei.com> (raw)
In pktgen_config_ports():
/* Start up the ports and display the port Link status */
for (pid = 0; pid < pktgen.nb_ports; pid++) {
…..
pktgen_rnd_bits_init(&pktgen.info[pid].rnd_bitfields);
}
And in pktgen_script_save()
for (i = 0; i < RTE_MAX_ETHPORTS; i++) {
info = &pktgen.info[i];
pkt = &info->seq_pkt[SINGLE_PKT];
range = &info->range;
if (info->tx_burst == 0)
continue;
(gdb) p info->tx_burst
$12 = 0
(gdb) p pktgen.info[31].tx_burst
$13 = 0
(gdb) p pktgen.info[30].tx_burst
$14 = 0
(gdb) p i
$15 = 32
Is this a bug?
Thx
发件人: Caianning
发送时间: 2016年9月14日 14:18
收件人: users@dpdk.org
抄送: Houzhipeng; 'Hu, Xuekun'
主题: pktgen segment fault when running save cmd
Hi
I got a segment fault when saving pktgen configurations:
Program received signal SIGSEGV, Segmentation fault.
0x000000000043db17 in pktgen_script_save (path=path@entry=0x7ffc1c1dced0 "/home/vmse/a/pktgen-nsh.cfg") at /home/vmse/a/pktgen-v3.0.09/app/pktgen-cmds.c:420
420 if (info->rnd_bitfields->active_specs) {
(gdb) p info
$2 = (port_info_t *) 0x8dfe08 <pktgen+280872>
(gdb) p info->rnd_bitfields
$3 = (struct rnd_bits_s *) 0x0
(gdb) p sizeof(*info)
$5 = 90322
Version of dpdk is 16.07, and version of pktgen is 3.0.09.
the cmdline is:
pktgen -c 0x1ff -n 3 -- -P -m "[1-2:3-4].0,[5-6:7-8].1"
Thx
next reply other threads:[~2016-09-14 6:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 6:34 Caianning [this message]
2016-09-14 13:23 ` Wiles, Keith
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=F994AE62EFA2864BAC5A2B81D86C27C13E2D4F23@nkgeml514-mbx.china.huawei.com \
--to=caianning@huawei.com \
--cc=houzhipeng@huawei.com \
--cc=users@dpdk.org \
--cc=xuekun.hu@intel.com \
/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).