Project

General

Profile

Bug #1752

Doomsday 1.14 crashes at startup when log level is set to verbose or x.verbose

Added by sunem over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Defect
Target version:
Start date:
2014-04-17
% Done:

100%

Tags:
Log

Description

It shows this text in a messagebox:

Application terminated due to exception:
Uncaught exception during loop iteration:
[Error_IllegalPatternError] (Log::Entry::str) Unknown format
character '#'

The other log levels doesn't seem to be affected by this.

Since there is no way to change the log options from outside of doomsday I have to delete 'persist.pack' in the runtime directory to get doomsday running again.

doomsday.out (14.5 KB) doomsday.out sunem, 2014-04-17 22:16

Related issues

Related to Bug #1769: [Snowberry] Obsolete log verbosity optionsClosed2014-04-18

Associated revisions

Revision e1c13e70 (diff)
Added by skyjake over 5 years ago

Fixed|Audio: Error in log output from SDL_Mixer plugin

There was a log message in the SDL_Mixer plugin where argument formatting
was incorrect, causing an exception during log flushing.

IssueID #1752

Revision 993c1d35 (diff)
Added by skyjake over 5 years ago

Fixed|Audio: Error in log output from SDL_Mixer plugin

There was a log message in the SDL_Mixer plugin where argument formatting
was incorrect, causing an exception during log flushing.

IssueID #1752

History

#1 Updated by skyjake over 5 years ago

  • Target version changed from 1.14 to 1.14.1

#2 Updated by skyjake over 5 years ago

  • Tags changed from Logging to Log

#3 Updated by skyjake over 5 years ago

  • Assignee set to skyjake
  • Priority changed from Normal to High

#4 Updated by skyjake over 5 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF