From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 ; Fri, 20 Apr 2018 04:03:55 +0200 (CEST) Received: by mail-pl0-f49.google.com with SMTP id 59-v6so4327890plc.13 for ; Thu, 19 Apr 2018 19:03:54 -0700 (PDT) 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=HhzaKoWs544XQrqeoOKzLpX6+8A6T0C2hiacu4wSB1w=; b=qE23LYNz/CEZTGUOy97lvRN/IpxGT11YydHXGlz/KznAXVAS82zQjP6D2X2qz9uSEv ICi9Q0M4pCN77Ln1mj6/KoOlojly48eg4lmKDXCD01dAWaeVp8eDbEZ79mPg+IKPEQrG 2/ETSb0qtykUogD8LWqvRjz+zRsudh2z1k766T9LnL04FO5PV4VV8U+EbiIfHQSESv+p 5hLnjp8HMaSYNy84bKoUk/I6d01ev/QMeMhDJlF//uGIgPn1z5ooxMK03+poYRIZdwim evQbl4FXmmljlFHpPFuhe13LwI7Kwo727TOepYoMby2LfXj4gEuMv1H3YUzX5taK0O4V rR7Q== 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=HhzaKoWs544XQrqeoOKzLpX6+8A6T0C2hiacu4wSB1w=; b=CroDlkIpC4Vu2Hikgd76FX0D96XV/1GTK429ZJWdoLsW5soSZMbuXS7zt1UCEmN6tg BFw6LbkVbwmG1QWRLGbxcLUSUkpxar9gaP2yN8YJZKmarScDx1rUzTxCgRHAwRveHqO7 RC7vmwO+jOBgnXICVLvi+LkPO6MXVDK5wWZkiG56V96dhR+STTkalcQhQzZ7wdgRJ9V1 T/kNkUz1GDvIDeIEKlBuWblpfayeOHARxJj7nV0sFt9cvzL1YlXLbfkSDSOKX7NIcfwn HDjhds+ZnBu7PV2cGIdXgwwRVH5EJCg/aDi+Dv/0CETxPir/s2/2RYF9k7LnWFF92a4Q pF6w== X-Gm-Message-State: ALQs6tA+fwldD1txua76WQ38pgVb+i/q0M2uxkZ5rA8LxAi2+QRnAkx0 X2UFs6gVJVL/iuU3OIOSTc6JSiCKipQ= X-Google-Smtp-Source: AIpwx4/vPz6lTajrJ1SN5tXtjK/5z3U0/V+q4mNekXyGLVxuzZsQ365+Yr3EYmNwPx8mNoeZ3jK6SQ== X-Received: by 2002:a17:902:6590:: with SMTP id c16-v6mr8292467plk.292.1524189834220; Thu, 19 Apr 2018 19:03:54 -0700 (PDT) Received: from xeon-e3 (204-195-71-95.wavecable.com. [204.195.71.95]) by smtp.gmail.com with ESMTPSA id t9sm9158606pgr.37.2018.04.19.19.03.53 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 19 Apr 2018 19:03:54 -0700 (PDT) Date: Thu, 19 Apr 2018 19:03:52 -0700 From: Stephen Hemminger To: shiva m Cc: dev@dpdk.org Message-ID: <20180419190352.3306580c@xeon-e3> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Apr 2018 02:03:55 -0000 On Fri, 20 Apr 2018 00:59:01 +0530 shiva m 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.