[Development] How to debug segfaulting test in Coin

[Toni Saario]

The CORE_FILES_PATH environment variable describes a path to a directory which will contain the core files in case of a segfault. These are then uploaded to Coin storage at the end of the job. As far as enabling that goes via coin scheduler, setting the CORE_FILES_PATH is possible via the customize feature in the scheduler by setting the environment variable, rest is done always/automatically. No printing will happen in the log from the core files. From technical view point it only specifies additional folder to upload at end of the job.

I am unsure about how much this has been ever used and I would think the easier way would be to acquire a Coin VM for debugging and with that reproduce the failure is available. This could also use input from developers with actual experience of debugging these cases.


Toni Saario
________________________________
From: Development <development-bounces at qt-project.org> on behalf of Konstantin Tokarev <annulen at yandex.ru>
Sent: Monday, September 21, 2020 7:28 PM
To: Qt Project Development Mailing-List <development at qt-project.org>
Subject: [Development] How to debug segfaulting test in Coin

Hello,

What is the usual procedure of debuggin test segfaults?

As far as I can see now all configurations print
"Skip uploading core files because CORE_FILES_PATH is not set in the environment"
so it's not possible to get any further then fact that test finished with segmentation fault.

Is there any way to enable core files in custom build configuration? If yes, will Coin
automatically load core and print backtrace to log or some other actions are needed?

--
Regards,
Konstantin

_______________________________________________
Development mailing list
Development at qt-project.org
https://lists.qt-project.org/listinfo/development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20200922/742f86a3/attachment.html>