DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev]  rte_panic SIGABRT core dump
@ 2018-04-19 19:29 shiva m
  2018-04-20  2:03 ` Stephen Hemminger
  0 siblings, 1 reply; 2+ messages in thread
From: shiva m @ 2018-04-19 19:29 UTC (permalink / raw)
  To: dev

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2018-04-20  2:03 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-04-19 19:29 [dpdk-dev] rte_panic SIGABRT core dump shiva m
2018-04-20  2:03 ` Stephen Hemminger

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).