[DiscordArchive] Are you using the gdb script that will print the whole assert log ?
[DiscordArchive] Are you using the gdb script that will print the whole assert log ?
Original source
Well, same as what I did, keep adding logs and check them
rektbyfaith
08-18-2025, 04:33 PM #11Archived author: jackpoz • Posted: 2025-08-18T16:33:14.352000+00:00
Original source
Well, same as what I did, keep adding logs and check them
Original source
Those issues are what made me add GetDebugInfo() to asserts
rektbyfaith
08-18-2025, 04:34 PM #12Archived author: jackpoz • Posted: 2025-08-18T16:34:09.422000+00:00
Original source
Those issues are what made me add GetDebugInfo() to asserts
Original source
In a perfect world there "should" be two types of asserts. I believe TC only implements one.
One that is always active, checks for critical errors that will lead to more problems and harder to debug issues later down an execution path
And another that is disabled in prod but enabled in debug (or alternatively converts to a log output), checks for general code sanity and logic, this one should be "abused" and applied all over.
I've personally always been a fan of the offensive programming methodology, to crash hard and early instead of silently returning
rektbyfaith
08-18-2025, 05:51 PM #13Archived author: Takenbacon • Posted: 2025-08-18T17:51:27.204000+00:00
Original source
In a perfect world there "should" be two types of asserts. I believe TC only implements one.
One that is always active, checks for critical errors that will lead to more problems and harder to debug issues later down an execution path
And another that is disabled in prod but enabled in debug (or alternatively converts to a log output), checks for general code sanity and logic, this one should be "abused" and applied all over.
I've personally always been a fan of the offensive programming methodology, to crash hard and early instead of silently returning
1 Guest(s)
1 Guest(s)