Crash Report Truncating Command Line?

Bugs that have been investigated and resolved somehow.

Moderator: GZDoom Developers

Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.
Post Reply
User avatar
Enjay
 
 
Posts: 27081
Joined: Tue Jul 15, 2003 4:58 pm
Location: Scotland
Contact:

Crash Report Truncating Command Line?

Post by Enjay »

I just reported a crash with Doom Tournament and when looking inside the crash report, I noticed that the command line was logged in local.txt like this:

Code: Select all

GZDoom version g3.8pre-747-g55e00f350 (55e00f350bc4df3a3deea1aaef7227b73c26de85)
Command line: "

Wad 0: gzdoom.pk3
However, the command line was actually:

Image


This seems likely to be unintended, hence the report.
_mental_
 
 
Posts: 3820
Joined: Sun Aug 07, 2011 4:32 am

Re: Crash Report Truncating Command Line?

Post by _mental_ »

Fixed in 025e502.

Please note that this didn't make crash reports Unicode-ready. I'm curious, do we really need it there?
If so, should the text be processed as wide characters and converted to UTF-8 before saving to a file?
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
Posts: 49234
Joined: Sat Jul 19, 2003 10:19 am
Location: Germany

Re: Crash Report Truncating Command Line?

Post by Graf Zahl »

Ideally it should convert the output from GetCommandLineW to UTF-8, but I do not think that this warrants any real work for the few cases where it's necessary.

BTW, I'd really wish that these stupid A/W #defines in windows.h could be disabled, they were the biggest roadblock in the transitioning phase because they let some code silently fail where a proper function would have caused a compilation error.
Post Reply

Return to “Closed Bugs [GZDoom]”