DPDK patches and discussions
 help / color / mirror / Atom feed
From: Daniel Kaminsky <daniel.kaminsky@infinitelocality.com>
To: sabu kurian <sabu2kurian@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Segmentation Fault on printf()
Date: Mon, 17 Mar 2014 21:45:48 +0200	[thread overview]
Message-ID: <CA+8v-JyPh5rA+01RwJ-idpkeraM0U8ZYhpHc9cpiUQOb1=36fg@mail.gmail.com> (raw)
In-Reply-To: <CAJ2bnfAt=guObm2VZuLrAfXiOGWdCZHhg4A_Ek-YdtwDbRS-bQ@mail.gmail.com>

Sabu,

I think that in this case the packet length is zero which will result in
nothing from mtod.

Daniel


On Sun, Mar 16, 2014 at 3:03 PM, sabu kurian <sabu2kurian@gmail.com> wrote:

> Hello chris,
>
> Thanks for your reply. I tried dumping the contents of mbuf as you have
> suggested.
> This is what I get:
>
> dump mbuf at 0x0x6c7620, phys=7f34d91eba28, buf_len=59488
> pkt_len=0, ol_flags=0, nb_segs=0, in_port=0
>
> and soon after that I get a segmentation fault. Do you have any idea on
> what could be causing it ?
>
> Regards
>
>
>
> On Fri, Mar 14, 2014 at 9:40 PM, Chris Wright <chrisw@redhat.com> wrote:
>
> > * 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 = &eth->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
> >
>

      reply	other threads:[~2014-03-17 19:44 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
2014-03-16 13:03   ` sabu kurian
2014-03-17 19:45     ` Daniel Kaminsky [this message]

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='CA+8v-JyPh5rA+01RwJ-idpkeraM0U8ZYhpHc9cpiUQOb1=36fg@mail.gmail.com' \
    --to=daniel.kaminsky@infinitelocality.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).