Arx Libertatis Bug Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Crash report #567  -  [D0A8DE1E] Unknown
Posted Oct 17, 2013 - updated Oct 17, 2013   Shortlink: http://arx.vg/567
action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
icon_info.png This issue is a duplicate of issue #547 - "[F72DCE6E] Unknown"
icon_info.png This issue has been closed with status "Not a bug" and resolution "DUPLICATE".
Issue details
  • Type of issue
    Crash report
  • Status
     
    Not a bug
  • Assigned to
    Not assigned to anyone
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     CrashBot
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
    Not determined
  • Resolution
    DUPLICATE
  • Priority
    Not determined
  • Reproducability
    Not determined
  • Severity
    Not determined
  • Targetted for
    icon_milestones.png Not determined
  • OS
    icon_customdatatype.png Linux
  • Architecture
    icon_customdatatype.png amd64
  • Fixed in
    icon_customdatatype.png Not determined
Issue description
Illegal storage access: address not mapped to object

GDB stack trace:
  1.  


Steps to reproduce this issue
Well, I was just looking on map (F4) and switched to level 1.

#1
icon_reply.pngReply
Comment posted by
 CrashBot
Oct 17, 06:47
A file was uploaded. arx.logicon_open_new.png This comment was attached:

arxcrash-11793-4038078855
#3
icon_reply.pngReply
Comment posted by
 CrashBot
Oct 17, 06:47
A file was uploaded. cfg.iniicon_open_new.png This comment was attached:

arxcrash-11793-4038078855
#4
icon_reply.pngReply
Comment posted by
 CrashBot
Oct 17, 06:47
A file was uploaded. crash.xmlicon_open_new.png This comment was attached:

arxcrash-11793-4038078855
#7
icon_reply.pngReply
Comment posted by
 Daniel Scharrer
Oct 17, 21:22
We believe this crash has been fixed in the 1.1.2 release. Please let us know if happens again.

The issue was updated with the following change(s):
  • The status has been updated, from New to Not a bug.
  • This issue has been closed
  • The resolution has been updated, from Not determined to DUPLICATE.