Projects
/
CODE-2546

Stack dump during BONUS processing

Description

16:34:16.557 SEVERE html-sheet-thread pcgen.io.ExportHandler replaceToken Error
replacing SKILL.5.ABMOD
java.lang.NullPointerException
at pcgen.core.BonusManager.sumActiveBonusMap(Unknown Source)
at pcgen.core.BonusManager.getTotalBonusTo(Unknown Source)
at pcgen.core.PlayerCharacter.getTotalBonusTo(Unknown Source)
at pcgen.core.analysis.SkillRankControl.getSkillRankBonusTo(Unknown Sour
ce)
at pcgen.core.analysis.SkillRankControl.getTotalRank(Unknown Source)
at pcgen.core.PlayerCharacter.includeSkill(Unknown Source)
at pcgen.io.exporttoken.SkillToken.getSkill(Unknown Source)
at pcgen.io.exporttoken.SkillToken.getToken(Unknown Source)
at pcgen.io.ExportHandler.replaceToken(Unknown Source)
at pcgen.io.ExportHandler.replaceLine(Unknown Source)
at pcgen.io.ExportHandler.processLoop(Unknown Source)
at pcgen.io.ExportHandler.loopFOR(Unknown Source)
at pcgen.io.ExportHandler.processLoop(Unknown Source)
at pcgen.io.ExportHandler.loopFOR(Unknown Source)
at pcgen.io.ExportHandler.write(Unknown Source)
at pcgen.gui2.facade.CharacterFacadeImpl.export(Unknown Source)
at pcgen.gui2.tabs.models.HtmlSheetSupport$DocumentBuilder.call(Unknown
Source)
at pcgen.gui2.tabs.models.HtmlSheetSupport$DocumentBuilder.call(Unknown
Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Environment

None

Activity

Show:
Tom Parker
April 6, 2014, 4:56 PM

Unfortunately, without line numbers this is VERY difficult to address to resolution.

I have attempted to code trade 6.2.1 to look at whether any of the variables in the method could EVER be null, and I find it hard to find a condition under which that could be true.

Tom Parker
June 30, 2014, 12:43 PM

due to lack of info, this is unable to be diagnosed. I am improving error messaging and hopefully this will be reported again

Tom Parker
June 30, 2014, 12:44 PM

Not technically fixed, as the trace is from a production version and thus does not have line numbers.

I have updated error messaging and that should help provide info in the future

Committed revision 24346.

Fixed

Assignee

Tom Parker

Reporter

Anonymous

Labels

None

Theme

None

Epic/Theme

None

Pending User Input

None

Fix versions

Affects versions

Priority

Minor
Configure