All of lore.kernel.org
 help / color / mirror / Atom feed
* QT5 application NOT generating core dump upon receiving segmentation fault
@ 2015-12-15 10:26 Ankur Tyagi
  2015-12-15 15:52 ` Denys Dmytriyenko
  0 siblings, 1 reply; 7+ messages in thread
From: Ankur Tyagi @ 2015-12-15 10:26 UTC (permalink / raw)
  To: meta-arago

[-- Attachment #1: Type: text/plain, Size: 871 bytes --]

 Hi,

I am running a QT5 based application on TI AM335x EVM kit. I am using
meta-arago daisy configuration.

My system is configured to generate core dump and core dumps are generated
whenever application receives segmentation fault (expected).

But when my QT5 based application received SIGSEGV, then no core dump is
generated. It dies without "Segmentation fault" message on stdout.

To debug this further, I added nullptr dereference in my application main()
before QApplication object is created and when executed, core dump was
created.
When I moved nullptr dereference after QApplication object is created, then
no core dump was created. Application died without any message.

So it seems QT is handling SIGSEGV and not allowing to create core dump.

Is it expected ? I believe not. What wrong am I doing and how to fix this ?

thanks
Ankur

[-- Attachment #2: Type: text/html, Size: 2544 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread
* QT5 application NOT generating core dump upon receiving segmentation fault
@ 2015-12-15 10:27 Ankur Tyagi
  2015-12-15 10:59 ` Julien Brianceau (jbriance)
  0 siblings, 1 reply; 7+ messages in thread
From: Ankur Tyagi @ 2015-12-15 10:27 UTC (permalink / raw)
  To: openembedded-devel

Hi,

I am running a QT5 based application on TI AM335x EVM kit. I am using
meta-arago daisy configuration.

My system is configured to generate core dump and core dumps are generated
whenever application receives segmentation fault (expected).

But when my QT5 based application received SIGSEGV, then no core dump is
generated. It dies without "Segmentation fault" message on stdout.

To debug this further, I added nullptr dereference in my application main()
before QApplication object is created and when executed, core dump was
created.
When I moved nullptr dereference after QApplication object is created, then
no core dump was created. Application died without any message.

So it seems QT is handling SIGSEGV and not allowing to create core dump.

Is it expected ? I believe not. What wrong am I doing and how to fix this ?

thanks
Ankur


^ permalink raw reply	[flat|nested] 7+ messages in thread
end of thread, other threads:[~2015-12-15 23:38 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-12-15 10:26 QT5 application NOT generating core dump upon receiving segmentation fault Ankur Tyagi
2015-12-15 15:52 ` Denys Dmytriyenko
2015-12-15 10:27 Ankur Tyagi
2015-12-15 10:59 ` Julien Brianceau (jbriance)
2015-12-15 11:05   ` Ankur Tyagi
2015-12-15 11:25     ` Julien Brianceau (jbriance)
2015-12-15 23:37       ` Ankur Tyagi

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.