On 04/19/2016 11:55 PM, Jerry James
wrote:
Yeah, but that means that we're just allowing silent null-pointer dereferencing. This can't be good: it probably just masks latent bugs: https://gcc.gnu.org/news/null.htmlOn Tue, Apr 19, 2016 at 8:50 PM, Richard Shaw <hobbes1069@xxxxxxxxx> wrote:I'm pretty much stumped on a problem where freecad (really python-pivy) segfaults on F24 but seems to run fine on F23 and I can't find any substantive difference between any of the packages. Strangely installing Coin3 from f23 on a f24 system seems to fix the problem...Try building Coin3 with -fno-delete-null-pointer-checks in the CFLAGS. I've had to add that to several packages on F24 to fix mysterious segfaults. I understand that in principle, a program that segfaults due lack of the null-pointer test must be doing the actual null pointer dereference first. We should test for that and log bugs against such code----or is it too much work for too little benefit? Is there a way to automate that, e.g. via abrt? |
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx