From mboxrd@z Thu Jan  1 00:00:00 1970
From: bugzilla@dpdk.org
Subject: [Bug 8] Debug/error output should go to stderr
Date: Tue, 09 Jan 2018 21:53:14 +0000
Message-ID: <bug-8-3@http.dpdk.org/tracker/>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
To: dev@dpdk.org
Return-path: <dev-bounces@dpdk.org>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

https://dpdk.org/tracker/show_bug.cgi?id=3D8

            Bug ID: 8
           Summary: Debug/error output should go to stderr
           Product: DPDK
           Version: 17.11
          Hardware: All
                OS: All
            Status: CONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: alexandre.ferrieux@orange.com
  Target Milestone: ---

In EAL and elsewhere, various diag, debug or error messages are just writte=
n to
stdout. This is completely incompatible with any application which generates
structured and/or binary output on its stdout. A library must confine such
unpredictable output to stderr.

--=20
You are receiving this mail because:
You are the assignee for the bug.=