Time Nick Message 19:19 sfan5 Krock: oh indeed I get lots of -Wnull-dereference warnings when compiling with lto 19:39 Krock hm? I get them without LTO 19:39 sfan5 didn't test without lto 19:39 MTDiscord Yeah just compiling the game there's warnings all over the place 19:40 MTDiscord I thought that was just accepted lol 19:40 Krock I followed a few of them, but there seems to be some false-positives, which is not helpful. 19:41 MTDiscord Are they initialized or set to null initially? 19:42 Krock array is first resized to 8 slots and then warns about accessing the data pointer which is guaranteed to exist (as far as I can tell) 19:42 Krock s/array/vector/ 19:45 MTDiscord Very simple, assert not null 19:45 MTDiscord It may fail if the system runs out of memory 19:45 MTDiscord Well, there are a few ways for that to fail but that can fail 20:08 MTDiscord jordan: bad alloc throws in C++ 20:08 MTDiscord out of curiosity, can you share the exact warning Krock? 20:12 Krock @luatic https://pastebin.com/raw/uNfXzjgP the first one is repeated a lot 20:13 Krock cross-reference to https://irc.luanti.org/luanti-dev/2026-08-22#i_6338437 20:34 sfan5 I didn't save the logs but I did get a bunch of warnings that would imply `this` to be null. not sure if that makes sense 21:03 MTDiscord Well I added cpp if (edges == nullptr) { return; } to the getEdges method and that removed the error 21:04 MTDiscord Probably should throw but that was a test, this is how I satisfied gcc in fortran C code 21:06 MTDiscord If you don't want a wall of suggestions for possible crash points, you must treat all those warnings as rust results 21:07 MTDiscord And it's probably good to throw in all those points because there may be ghost bugs that no one has discovered yet