bugBattle for Wesnoth - Bugs: bug #21093, Bank teller crashes next load of...

 
 
Show feedback again

bug #21093: Bank teller crashes next load of test scenario

Submitted by:  J Tyne <jamit>
Submitted on:  Mon Sep 2 19:55:50 2013  
 
Category: BugSeverity: 5 - Blocker
Priority: 5 - NormalItem Group: WML
Status: FixedPrivacy: Public
Assigned to: Ignacio R. Morelle <shadowmaster>Open/Closed: Closed
Release: 1.11.6+devOperating System: Linux

Add a New Comment (Rich MarkupRich Markup):
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Sun Oct 5 23:40:50 2014, comment #3:

Fixed in master and 1.12.

Ignacio R. Morelle <shadowmaster>
Project AdministratorIn charge of this item.
Thu May 8 22:05:35 2014, comment #2:

<iceiceice> does anyone else get an immediate segfault when they run the test scenario?
<iceiceice> sorry, not exactly segfault...
<iceiceice> when i run "wesnoth -t", about a quarter of a second after start of scenario, my window dissappears and i get this assertion failure:
<iceiceice> http://pastebin.com/LcsdGSvc
<iceiceice> hmm actually it doesnt happen after i deleted my persistent variables file
<iceiceice> the file was .../1.13/persist/demo.cfg, and its contents were this: http://pastebin.com/XxxUzKmR
<iceiceice> idk i think its reproduceable
<iceiceice> hmm it looks like that file is made whenever you step on the bankteller hex, and ruins all future test scenario runs :/

  • irker566 has quit (Quit: transmission timeout)

<iceiceice> oh i guess this is a known bug hmm

Chris Beck <involution>
Project Member
Mon Sep 2 21:02:41 2013, comment #1:

Forgot to mention: The "Bank Teller" hex is at 10,6.

J Tyne <jamit>
Project Member
Mon Sep 2 19:55:50 2013, original submission:

I ran the test scenario (wesnoth -t) and stopped by the "Bank Teller" hex. The following was stored in persist/demo.cfg:

The next time I tried to run the test scenario, I got a segmentation fault. Clearing the contents of persist/demo.cfg caused the crash to go away.

Upon doing a code trace, I found the culprit lying in persist_file_context::clear_var(), where a null pointer is being dereferenced. I'll change that to an assertion failure shortly so that the error message is more meaningful, but a fix would need to come from someone who knows how the persistent variable code is supposed to work.

J Tyne <jamit>
Project Member

 

(Note: upload size limit is set to 1024 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by involution (Posted a comment)
  • -unavailable- added by shadowmaster (Updated the item)
  • -unavailable- added by soliton (Updated the item)
  • -unavailable- added by jamit (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Error: not logged in

     

     

    Follow 5 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Sun Oct 12 12:18:27 2014shadowmasterOpen/ClosedOpen=>Closed
    Sun Oct 5 23:40:50 2014shadowmasterStatusNone=>Fixed
      Assigned toupthorn=>shadowmaster
    Wed Dec 18 23:25:52 2013shadowmasterSeverity3 - Normal=>5 - Blocker
    Mon Sep 2 22:29:01 2013solitonAssigned toNone=>upthorn
    Show feedback again

    Back to the top


    Powered by Savane 3.1-cleanup