Conversation

Notices

1. Embed this notice
   翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Sunday, 04-Feb-2024 13:32:04 JST 翠星石

   in reply to

   • T man :sex: :puffgiga: :puffpowerroll:
   @theorytoe Since undefined behavior may not usually lead to a crash during certain complications, but not others.
   
   One example would be forgetting a null terminator - sometimes gcc will add some null padding after arrays for alignment, resulting in the software working just fine (over-reading 1 null byte is very unlikely to lead to a segfault), but if the memory layout changes in the slightest, padding for alignment may no longer be required, meaning the reader blows past the end of the array and into "protected" memory and therefore causes a segfault.
   
   I suggest compiling with -march=native -O3 as that tends to reveal the undefined behavior right when you make it.
   • Embed this notice
     T man :sex: :puffgiga: :puffpowerroll: (theorytoe@ak.kyaruc.moe)'s status on Sunday, 04-Feb-2024 13:32:05 JST T man :sex: :puffgiga: :puffpowerroll:
     why am I so reatarded I throw all the functionality in one func and it works fine
     
     but the MOMENT i split it out it fucking segfaults