For some odd reason after returning from an crashed UFO mission and trying to hire/fire a new Agent I get a crash related to character overflow. I did some previous attempt where I tried to provoke this bug but it doesn't happen by making one of the agent name very long. I will need to do additional testing where I can reproduce this bug 100%.
It's not necessarily related to a buffer overflow. The warning you see there means that the name is too long to fit in the bounding box of the control.
If you can get a stack trace with gdb that would be great
Alright I will try to test a bit more often to see if it was actually buffer overflow related with the character strings or not. I thought it was related to that because the log at the end shows only those things and nothing more.
Edit: gdb stacktrace OpenApoc_Char_Overflow_gdb.txt, happened again after returning from a UFO crash mission while trying to hire&fire a agent.
If you manage to reproduce this bug, can you run info stack in gdb after receiving the segv signal? Knowing which line generated the error helps a lot but a complete stack trace will help to narrow the list of controls that can cause this.
Sorry I forgot to mention this in my first comment
Cannot reproduce, I think the issue was fixed in #595.
Closing as requested by emptyVoid
If the problem returns, please create a new issue and reference this as appropriate
Most helpful comment
It's not necessarily related to a buffer overflow. The warning you see there means that the name is too long to fit in the bounding box of the control.
If you can get a stack trace with gdb that would be great