It's been a while since I dug into the code any myself, but I could probably help out a bit as well.
I've gone through code before checking for obvious buffer overflow functions sprintf etc. Something like that is doable. I've a laptop to re-install over this weekend, it might have a new enough GCC (7.3, but GCC8 is an option) to cause issues... my current desktop is only GCC 5. Or I could spin up a VM with something newer. Cheers John EI7IG On 19/04/2019 20:31, Curt Mills wrote: > On Fri, Apr 19, 2019 at 11:30 AM Tom Russo <[email protected]> wrote: > >> If we want to release again after we stabilize a little, I'd be OK with it, >> but I really doubt I'll be able to get the warning issue in hand anytime >> this >> month. Unless, perhaps, someone would like to join in the fun and we could >> divide up the work. >> > I might be able to help a little here and there. I can remember doing the > same thing way back when a couple of times (I'm coming up on 20 years on > this one project!). At more than one point in the project I had it down to > zero errors/warnings. Then another GCC version came out each time. > > One thing we could also perhaps do is change the compile flags to issue > fewer warnings, but of course wouldn't want to turn off ones that are real > and might have implications if we don't correct our code. Don't want to > hide real problems. > _______________________________________________ Xastir-dev mailing list [email protected] http://xastir.org/mailman/listinfo/xastir-dev
