From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg1-f173.google.com (mail-pg1-f173.google.com [209.85.215.173]) by dpdk.org (Postfix) with ESMTP id 5CD6A1BD48 for ; Fri, 21 Dec 2018 04:10:17 +0100 (CET) Received: by mail-pg1-f173.google.com with SMTP id z11so1825393pgu.0 for ; Thu, 20 Dec 2018 19:10:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=6us7xBSbhXC8zhS8Xkb6Tx1a7s+d7y/iuQaVeWTXFh8=; b=emo6BxRFgYCxCJe31QguEuboXGi5KXpW4qvlwwHeji+e8PH93o+XzH4seol0NehnxY kBAf3bpaa6NxgMVCti0JVfJBXSRxtBofMOqiYUTYn/Kv+0ZC6fkP8D63s21TqH58U9pG RuEp3HKOYEhPzw5xL6yR2Hx/W/gMWLGqCTJ9BkKPL0kqxf2Jzqce+I2P9vlgD9Ul1Toq 9pkEplQL5zAzZHleAAcJRDxioAoadPizoYwbZzEMFGCavTBia/12xP81LszEk6O+CpnL UPZIDgC468fOdktZDH2ON2/rOcKXqZoyetJblrzhg4NL6Oix9iwx5kZ8QsAdZNnvo+wF ogsg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=6us7xBSbhXC8zhS8Xkb6Tx1a7s+d7y/iuQaVeWTXFh8=; b=LdengbNhc8liRoBh0Iz+3JxABnqwQ3tMdty+hiN5LfhjgHmSKQEuyqRp+vOx0YH7rv 2jduzfaviaUykrYhTnzrdqbv2GQVTycugcMBFnzfvh38QIhtWoIp8SbsK+j1LrGyj4ZD NM6E1o2SzJrzXZMQ0j3fpN447pSK+sy5fEpGFnoLAyLyoZ3sBtKou//gBtvMho8t2kAa Tz3/vxFpNQNkyODQrG+cg7/NUb22kzFsqng6e1d2ph0OoGdeIZgQRITzRCrmqu3uBh7R QU5nwHjHPe+dc6SVuiJhzKM6PucBVUI0QTZdGevM9bmvgkhR8WdjpYcorOdXXhXv4lYo 8aCA== X-Gm-Message-State: AJcUukfrWQnvXhFSDXbnaUF1lJPO7/M3eDri4Jo3qwJjTWxA2EEDjlwH yB7P+BJDWlO6pS+yZl9dazneHmD8TzE= X-Google-Smtp-Source: ALg8bN7mJO/Hh/f/Qa08AlrMcCP44lJlOz4LDnORFaiDnSzNRK82z2JPSWYDzGv18nHPU1dHWyTHZw== X-Received: by 2002:a63:7c41:: with SMTP id l1mr735959pgn.45.1545361816313; Thu, 20 Dec 2018 19:10:16 -0800 (PST) Received: from xeon-e3 (204-195-22-127.wavecable.com. [204.195.22.127]) by smtp.gmail.com with ESMTPSA id f67sm31671235pfc.141.2018.12.20.19.10.16 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 20 Dec 2018 19:10:16 -0800 (PST) Date: Thu, 20 Dec 2018 19:10:13 -0800 From: Stephen Hemminger To: Hideyuki Yamashita Cc: "users@dpdk.org" Message-ID: <20181220191013.358bebd8@xeon-e3> In-Reply-To: <201812210049.wBL0nPMM001632@ccmail04.silk.ntt-tx.co.jp> References: <201812210049.wBL0nPMM001632@ccmail04.silk.ntt-tx.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-users] How to show debug log in DPDK and DPDK application X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Dec 2018 03:10:17 -0000 On Fri, 21 Dec 2018 09:48:04 +0900 Hideyuki Yamashita wrote: > Hello > > I am a developer for DPDK application(SPP). > And I have a very basic question how to debug by > increasing log level. > > Q1.Are thre any documents those describe the following? > - how to output debug log of DPDK > - how to output debut log of DPDK application > > As I did quick search on Google, no official documents found. > If above is yes. > Please let me know how to achieve those. > > Thanks in advance for your guidance to newbie! > > BR, > Hideyuki Yamashita > NTT TechnoCross > > logging in current DPDK is controlled per subsystem. See: rte_log_set_level_pattern and rte_set_level This can be set on command line or with API. The default log output on DPDK is to stdout of the application. This is not useful for a long running service like a daemon, but the log can be captured by either opening a file and using: rte_openlog_stream Or also by using glibc stdio function open_memstream to make a memory stream and pass that. This requires a bit more setup.