From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 5799AA0543; Wed, 12 Oct 2022 17:16:40 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 48F8643027; Wed, 12 Oct 2022 17:16:40 +0200 (CEST) Received: from mail-pj1-f48.google.com (mail-pj1-f48.google.com [209.85.216.48]) by mails.dpdk.org (Postfix) with ESMTP id 205C642EF7 for ; Wed, 12 Oct 2022 17:16:39 +0200 (CEST) Received: by mail-pj1-f48.google.com with SMTP id l1-20020a17090a72c100b0020a6949a66aso2355946pjk.1 for ; Wed, 12 Oct 2022 08:16:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=qnztyDiFRHBfENREo5QPc0T127/iDDq/a6PTEnwjav4=; b=FmssS/0R4zMdQSnbM+JTx37BJ5e5ckq8HJsu+QohDempAbUsO2DbYjxJ7Z3ETNfjmq GYBWfx5ppiP5OM46cmsK1t6N/gr2Gwd67690DIwsIS5arWxCGf44e7OKu7zPZvW04Sct RTfm3gucKBJGuyXxX0IjSvvWQSyxV25xPLguc+wfIqSNZ7jB/pvGzS1F1Jd1S0T4b/+x 7dtg9RArZ2Z4zQDBfXv/iUhqIokutYnN7GEOydfOmOkkoVsw2sUnXw05msifXp7D5asu 8Z1aHxoHRn9BjdRkrJNGFqTf+P4nvAADPJze3JLRn8TZqo/mAX59j1gfFgRhIi7dljSn tBmA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=qnztyDiFRHBfENREo5QPc0T127/iDDq/a6PTEnwjav4=; b=1nyoAamqWHo9kvH33+pSaeKThU76QmX4G5FxVTmABPzRU3dteLa2fz40R538NIiAgR VeDdBhk5yADJJVKWxTcmMb/6gtEeBE2iyvxtpk2utZ2ABzfq/UPOYhAdj5eYyBcapFKz fqlGbWyDB2u6rv+vfNkvglpL/xQaVpZNMHu1hpfMCWFFGg3H0vz5xU7XyMMK6/iTrFSG V4OkF5gxwnwyFS+FzbfJccDoKHL7WqBApUC44KGQZaINmjPT/2k5NNfyTbPK1GjGPF76 FTdVigACbcV8/R1bMNV5XvWKDCPH0IWu6hNNXCScT4TLxuFfcqhr5BrwmZqFzoMqIrI/ H8nA== X-Gm-Message-State: ACrzQf0d8nUinxZWdLOwfj+0QEm6E0Wg8gOqGgWWERWj3MJKr2q0jXVe N49KO3NH6BBkSlW6VTYS/iIANw== X-Google-Smtp-Source: AMsMyM6Tr06BDIcY3NFm74vT0PzP22DgvRGdlQ0n4EJqF7B+ME7U9GFHCKCrOMp3aBfAdw33xJ+Lvg== X-Received: by 2002:a17:90b:1d8b:b0:20d:30a5:499e with SMTP id pf11-20020a17090b1d8b00b0020d30a5499emr5808770pjb.84.1665587798258; Wed, 12 Oct 2022 08:16:38 -0700 (PDT) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id z19-20020aa79593000000b0056316f0b7f8sm6758pfj.33.2022.10.12.08.16.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 12 Oct 2022 08:16:38 -0700 (PDT) Date: Wed, 12 Oct 2022 08:16:36 -0700 From: Stephen Hemminger To: Sylvia =?UTF-8?B?R3J1bmR3w7xybWVy?= Cc: "dev@dpdk.org" Subject: Re: DPDK PDUMP pcapng usage Message-ID: <20221012081636.4639ac16@hermes.local> In-Reply-To: <1f5f87b63b94410fb651546d1b4a0937@b-plus.com> References: <1f5f87b63b94410fb651546d1b4a0937@b-plus.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Tue, 11 Oct 2022 15:11:02 +0000 Sylvia Grundw=C3=BCrmer wrote: > Hi, >=20 > i am running DPDK 22.03 on a NXP platform, using 2 eth ports (dpmac, dpni= , dprc config should be OK, as i get bursts of packets with testpmd and in = a little customized app > which is just checking if packets are bursted in mempool. >=20 > So then i tried to use pdump and pcapng to write out a capture.pcapng fil= e. >=20 > I created mempool and ringbuffer according tot o the dumpcap-example, (rt= e_eth_dev_configure, rte_eth_dev_adjust_nb_rx_tx_desc, rte_eth_rx/tx_queue_= setup, rte_eth_dev_start with the portid i have and which was veryfied by m= y little customized app as working properly) > but when i call enable_pdump i am running into a segmentation fault. >=20 > Validation of port, ring, mp, flags are ok. > the problem seems to come from snprintf. There is no different behaviour = no matter if i use enable_pdump or enable_pdump_by_deviceID or enable_pdump= _bpf. > PDUMP seems to have trouble whith my portID or deviceID. >=20 > Can you give any hint, what might go wrong here? Or what i could try to g= et this stuff running? > Thanks in advance. >=20 > [cid:image003.png@01D8DD94.70449230] Sample code would help, and the dpdk mailing list blocked your image attach= ment