This is the way I feel right now.
Been working on this program, everything was working fine. Second I implement the disk writing part to dump it's data, all hell breaks loose. If I comment out the part that writes to disk, It's fine... problem is, the issues are completely unrelated to the disk. so it really has me scratching my head.
Fuuuuuuuuuuuuuuuuu
Could be worse though, at least it's not a segfault that always happens at a random part of the program. Those are the worse.
This is the way I feel right now.
Been working on this program, everything was working fine. Second I implement the disk writing part to dump it's data, all hell breaks loose. If I comment out the part that writes to disk, It's fine... problem is, the issues are completely unrelated to the disk. so it really has me scratching my head.
Fuuuuuuuuuuuuuuuuu
Could be worse though, at least it's not a segfault that always happens at a random part of the program. Those are the worse.
what language
C++.
I'm suspecting I have a bad new/delete somewhere, just need to find it. My app currently does not have a way to exit so I'm implementing that using a pid file that gets deleted. Then I'll run it through valgrind and go from there. I can ctrl+C out but that's not an accurate way to check. I'll need the pid file when I make the service start/stop script anyway.
Last night I did have a seg fault but it was always at the same spot so a bit easier to pin point than the ones that are random. Couple hours wasted on that, turned out to be something really silly, as normal.![]()
LOL![]()
I think I had one of those once.