Hi Richard, I had the same, I didn't completely dig into it, but I think an underlying library (qca?) uses this signal for some kind of internal communication.
I ignored it by going to Tools -> Options -> Debugger -> GDB and in Additional Startup Commands I added handle SIG33 pass nostop noprint If someone has a clue why this is suddenly required, I'll be interested in knowing. Regards Matthias On 12/24/18 1:35 PM, Richard Duivenvoorde wrote: > Hi Devs, > > Currently I fail to be able to debug QGIS master in QtCreator as I did > some time ago on this same machine. > > A fresh checkout compiles fine, and I can RUN it fine (both from withing > QtCreator OR just by running it from the output/bin folder). > > But already several attempts to start a debug session fail during the > setup of the ui with a QtCreator dialog telling me: > > The inferior stopped because it received a signal from the operating system. > Signal name: SIG33 > Signal meangin: Real-time event 33 > > QtCreator at that time looks like: > > http://duif.net/temp/crash1.png > > QGIS at that time is showing the splash screen and showing "Setting up > the GUI".. > > Anybody a clue? > > Regards, > > Richard Duivenvoorde > _______________________________________________ > QGIS-Developer mailing list > [email protected] > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer > -- Matthias Kuhn [email protected] <mailto:[email protected]> +41 (0)76 435 67 63 <tel:+41764356763> OPENGIS.ch Logo <http://www.opengis.ch>
_______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
