From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: rte_panic SIGABRT core dump
Date: Thu, 19 Apr 2018 19:03:52 -0700
Message-ID: <20180419190352.3306580c@xeon-e3>
References: <CAGm0vUoWUD4jJfCixMW6=b5ys8x2Lpjf3KB4oo9HHedMZYf-gg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: dev@dpdk.org
To: shiva m <anjaneya2@gmail.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-pl0-f49.google.com (mail-pl0-f49.google.com
 [209.85.160.49]) by dpdk.org (Postfix) with ESMTP id 19F87A84F
 for <dev@dpdk.org>; Fri, 20 Apr 2018 04:03:55 +0200 (CEST)
Received: by mail-pl0-f49.google.com with SMTP id 59-v6so4327890plc.13
 for <dev@dpdk.org>; Thu, 19 Apr 2018 19:03:54 -0700 (PDT)
In-Reply-To: <CAGm0vUoWUD4jJfCixMW6=b5ys8x2Lpjf3KB4oo9HHedMZYf-gg@mail.gmail.com>
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>

On Fri, 20 Apr 2018 00:59:01 +0530
shiva m <anjaneya2@gmail.com> wrote:

> 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

Fix the code in rte_eal_init don't try to catch abort and continue
that is dead end.