From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <anjaneya2@gmail.com>
Received: from mail-it0-f42.google.com (mail-it0-f42.google.com
 [209.85.214.42]) by dpdk.org (Postfix) with ESMTP id 27184AA99
 for <dev@dpdk.org>; Thu, 19 Apr 2018 21:29:03 +0200 (CEST)
Received: by mail-it0-f42.google.com with SMTP id f6-v6so8459608ita.2
 for <dev@dpdk.org>; Thu, 19 Apr 2018 12:29:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=mime-version:from:date:message-id:subject:to;
 bh=pBhwhJcTGMLA2FwCB3tFqPmdbGSwb92UIj5Qw4XOrvc=;
 b=FAF6BcW40J2HggSFVGL1J+4Bn3v2xtF6dlX+y8cA4CmLmSrT127dnp6VX4HsNlZ8TQ
 0UktFJhk40nuiuo0bYAoGeIlHbUVBHH31s4eeK1ZLS8O+lmcqALfw9EwMnOCrI+1dNIV
 yiT4+ZMgs86wvF3vTdtSPM5gXzGuGYQUYSU/vwps1/MtylclGew2/lGntTVG8L34WupS
 0yHcGcFzf4wujMjH++0haWXbEkuNj4bvcyxfhZAceHMg85o3ATRdO8dnglpgnxF8WhPk
 NdnMaVElByJ8RvBYvV6ulra5GfXw46dkG0pLL99/bBNpkqVjbKRrbS9RvNCXXQFReqMW
 4APA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
 bh=pBhwhJcTGMLA2FwCB3tFqPmdbGSwb92UIj5Qw4XOrvc=;
 b=mMcVvYChWqSY4FXuAEvmP5Z4O9jcL67tn2uaF25vJDoFcFMYFx6YS44au1vlLlaPKF
 U+FxFmsZZCPxxBmC5kQ0mPwL1HTKxsUn82sWdyhneNBObdGW6zBTIfUL4DXkxoEnosGR
 e3+bUEoFJw/rxS7jej/MWlIdyVSGHQ00ceBj0XyI+qMt9JtAnROoy3KSco3/Xsjlq/G+
 4ygtHsew7iTuFrelZE5aB5aoBnrEIaSwCROEOjR0c8wYpKzuNoxrerbFXMuGFuM45kDs
 vnv4D2c0OYso54NhNUdUVWXb0ei+Z+CQNkKsyXf1TGNEV47LHGxURFgGguw6ru16DprI
 W/PQ==
X-Gm-Message-State: ALQs6tCRjkWaMuhMQxbPQ/mhGxaymUrZlnhrT+CVjr8goTmA81YyfTfg
 +kLEtG45f1RLnl9S8uthXA4osz8qEbEViyvfQCYopg==
X-Google-Smtp-Source: AIpwx491rIB32eJhlL6hyagSyhGmFQ0QZX8BBSx9tkHwkGkAz7p5kFXJP9/enS1MpSn0CPmHsgR9CIzHaq0OSMe1NfA=
X-Received: by 2002:a24:c644:: with SMTP id j65-v6mr49833itg.109.1524166142117; 
 Thu, 19 Apr 2018 12:29:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a02:59a:0:0:0:0:0 with HTTP;
 Thu, 19 Apr 2018 12:29:01 -0700 (PDT)
From: shiva m <anjaneya2@gmail.com>
Date: Fri, 20 Apr 2018 00:59:01 +0530
Message-ID: <CAGm0vUoWUD4jJfCixMW6=b5ys8x2Lpjf3KB4oo9HHedMZYf-gg@mail.gmail.com>
To: dev@dpdk.org
Content-Type: text/plain; charset="UTF-8"
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-dev]  rte_panic SIGABRT core dump
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
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>
X-List-Received-Date: Thu, 19 Apr 2018 19:29:03 -0000

Hi,

Need help in avoiding core dump in case rte_eal_init() fails in some
special cases.

Part of my code causing rte_panic during system bootup and causes a core
dump. I do not want this core dump.

I tried catching SIGABRT in my application and did _exit() in my handler.
Still I see core dump file getting generated.

If I manually raise(SIGABRT) in my app, I do not see core dump. My SIGABRT
handler not working if SIGABRT raised by rte_eal_init() and it causes core
dump.

Can someone help in avoiding core dump in case rte_eal_init() cause
rte_panic.

Thanks,
Shiva