From: Chris Wright <chrisw@redhat.com>
To: sabu kurian <sabu2kurian@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Segmentation Fault on printf()
Date: Fri, 14 Mar 2014 09:10:47 -0700 [thread overview]
Message-ID: <20140314161047.GD1390@x220.localdomain> (raw)
In-Reply-To: <CAJ2bnfDcs9OiycSFcC9CvSihJ=u6vQt5ema_VMjseq-CiDsqBQ@mail.gmail.com>
* sabu kurian (sabu2kurian@gmail.com) wrote:
> Hello friends,
>
> I'm trying to print the ether_type for a packet that I captured from a port
> on my machine. Suppose 'm' holds the packet. 'm' is of type 'struct
> rte_mbuf'. Intels API reference for DPDK says 'ether_type' is of uint16_t.
> I used the following code to retrieve ether_type.
>
> void * eth_type;
> struct ether_hdr *eth;
>
> eth = rte_pktmbuf_mtod(m, struct ether_hdr *);
> eth_type = ð->ether_type;
>
> printf("\n Type is %" PRIu16 , *((uint16_t *)eth_type));
Looks ok, albeit slightly overly complicated.
struct ether_hdr *eth;
uint16_t eth_type;
eth = rte_pktmbuf_mtod(m, struct ether_hdr *);
eth_type = eth->ether_type;
printf("\n Type is %" PRIu16 , eth_type));
This would remove all the extra casting. Perhaps the mbuf is the problem
here. And if so, the above snippet would segfault on eth->ether_type
showing you that mbuf is invalid.
You could try to (above mtod):
rte_pktmbuf_dump(m, sizeof(struct ether_hdr));
as that will show key contents of mbuf and packet data (and do some
basic validation along the way).
thanks,
-chris
next prev parent reply other threads:[~2014-03-14 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 10:27 sabu kurian
2014-03-14 16:10 ` Chris Wright [this message]
2014-03-16 13:03 ` sabu kurian
2014-03-17 19:45 ` Daniel Kaminsky
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=20140314161047.GD1390@x220.localdomain \
--to=chrisw@redhat.com \
--cc=dev@dpdk.org \
--cc=sabu2kurian@gmail.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).