From: Stephen Hemminger <stephen@networkplumber.org>
To: shiva m <anjaneya2@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] rte_panic SIGABRT core dump
Date: Thu, 19 Apr 2018 19:03:52 -0700 [thread overview]
Message-ID: <20180419190352.3306580c@xeon-e3> (raw)
In-Reply-To: <CAGm0vUoWUD4jJfCixMW6=b5ys8x2Lpjf3KB4oo9HHedMZYf-gg@mail.gmail.com>
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.
prev parent reply other threads:[~2018-04-20 2:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 19:29 shiva m
2018-04-20 2:03 ` Stephen Hemminger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180419190352.3306580c@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=anjaneya2@gmail.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).