[DiscordArchive] Hey team, I just compiled the latest TrinityBot build and both EXE crash before they can start so th
[DiscordArchive] Hey team, I just compiled the latest TrinityBot build and both EXE crash before they can start so th
Original source
Hey team, I just compiled the latest TrinityBot build and both EXE crash before they can start so there's no logs. I haven't updated in about a month and I've checked for recent commits that highlight other areas I might have missed but I am not seeing anything glaring.
MS Event Logs just saying faulting module was MSVCP140.dll - built again and same issue.
Anyone else experienced something similar in the last month - nothing is showing in Issues; I am sure it's something simple I am missing. Thoughts?
rektbyfaith
06-02-2024, 08:43 AM #1Archived author: Frank Dux • Posted: 2024-06-02T08:43:23.528000+00:00
Original source
Hey team, I just compiled the latest TrinityBot build and both EXE crash before they can start so there's no logs. I haven't updated in about a month and I've checked for recent commits that highlight other areas I might have missed but I am not seeing anything glaring.
MS Event Logs just saying faulting module was MSVCP140.dll - built again and same issue.
Anyone else experienced something similar in the last month - nothing is showing in Issues; I am sure it's something simple I am missing. Thoughts?
Original source
Any changes made within last month+ that require maps to be redone?
rektbyfaith
06-02-2024, 08:50 AM #2Archived author: Frank Dux • Posted: 2024-06-02T08:50:36.364000+00:00
Original source
Any changes made within last month+ that require maps to be redone?
Original source
if you want usable crash logs, compile in debug or relwithdebinfo mode, not release
rektbyfaith
06-02-2024, 09:13 AM #3Archived author: Tea • Posted: 2024-06-02T09:13:16.561000+00:00
Original source
if you want usable crash logs, compile in debug or relwithdebinfo mode, not release
Original source
then look for them inside Crashes folder right where the executables are
rektbyfaith
06-02-2024, 09:13 AM #4Archived author: Tea • Posted: 2024-06-02T09:13:35.200000+00:00
Original source
then look for them inside Crashes folder right where the executables are
Original source
we do not write anything to system event logs
rektbyfaith
06-02-2024, 09:13 AM #5Archived author: Tea • Posted: 2024-06-02T09:13:53.523000+00:00
Original source
we do not write anything to system event logs
Original source
These are built with relwithdebinfo and that option is never touched - but there were no crash logs generated in the Crash folder - these are failing on initial launch.
rektbyfaith
06-02-2024, 09:25 AM #6Archived author: Frank Dux • Posted: 2024-06-02T09:25:50.893000+00:00
Original source
These are built with relwithdebinfo and that option is never touched - but there were no crash logs generated in the Crash folder - these are failing on initial launch.
Original source
I did update VS2022 to 17.10.1 recently if it's related in any way.
rektbyfaith
06-02-2024, 09:28 AM #7Archived author: Frank Dux • Posted: 2024-06-02T09:28:12.051000+00:00
Original source
I did update VS2022 to 17.10.1 recently if it's related in any way.
1 Guest(s)
1 Guest(s)