Arx Libertatis Bug Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Crash report #229  -  [3852110D] strcasecmp () from /lib/libc.so.6
Posted Apr 20, 2012 - updated Jul 05, 2013   Shortlink: http://arx.vg/229
action_vote_minus_faded.png
0
Votes
 action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Fixed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Crash report
  • Status
     
    		 Fixed
  • Assigned to
    Not assigned to anyone
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    Guest user
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
    Not determined
  • Resolution
    RESOLVED
  • Priority
    Not determined
  • Reproducability
    Not determined
  • Severity
    Not determined
  • Targetted for
    icon_milestones.png Not determined
  • OS
    icon_customdatatype.png Not determined
  • Architecture
    icon_customdatatype.png Not determined
  • Fixed in
    icon_customdatatype.png Arx Libertatis 1.0.1
Issue description
Illegal storage access: address not mapped to object

GDB stack trace: 
  1. [Thread debugging using libthread_db enabled]
  2. 0x080990dc in ?? ()
  3. [Current thread is 1 (Thread 0xb6d4a6e0 (LWP 22421))]
  4.   Id   Target Id         Frame 
  5. * 1    Thread 0xb6d4a6e0 (LWP 22421) "arx" 0x080990dc in ?? ()
  6.  
  7. Thread 1 (Thread 0xb6d4a6e0 (LWP 22421)):
  8. #0  0x080990dc in ?? ()
  9. No symbol table info available.
  10. #1  <signal handler called>
  11. No symbol table info available.
  12. #2  0xb71e44f3 in strcasecmp () from /lib/libc.so.6
  13. No symbol table info available.
  14. #3  0x08160510 in logger::CriticalErrorDialog::~CriticalErrorDialog() ()
  15. No symbol table info available.
  16. #4  0x08160a08 in ?? ()
  17. No symbol table info available.
  18. #5  0x0825729d in main ()
  19. No symbol table info available.

Steps to reproduce this issue



#3
icon_reply.pngReply
Comment posted by
Daniel Scharrer
Apr 20, 23:56
This is a bug in the critical error dialog and has now been fixed for the next release.

It only happens for desktop environments that don't define the DESKTOP_SESSION environment variable, so you can work around it by running arx as: 

 DESKTOP_SESSION=whatever arx


It also happens if there is a critical (startup) error anyway that prevents the game from running, most likely missing data files. You can see where the game looks for the data files by running 

 arx --list-dirs


also see the wiki arcticle on the data directories and installing the game data under linux. If you correctly install the game data correctly, the game won't trigger this bug (unless there is another critical error).

If installing the data files does not fix the issues, arx should have created an arx.log file in the user directory (see the data directories wiki article) containing the error that would have been displayed in the dialog.

#4
icon_reply.pngReply
Comment posted by
Daniel Scharrer
Apr 23, 07:50
This has been fixed in version 1.0.1.