Arx Libertatis Bug Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report #164  -  Crash Handler: arxcrashreporter isn't always started under linux.
Posted Feb 27, 2012 - updated Mar 13, 2012   Shortlink: http://arx.vg/164
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
    Bug report
  • Status
     
    		 Fixed
  • Assigned to
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    Daniel Scharrer
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Time spent
    369549 hours
  • 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 Not determined
Issue description
It seems as if the signal handler crashes.

We should really do as little as possible in the crash handler as the process is already in an unpredictable state.
Steps to reproduce this issue
Nothing entered.

#7
icon_reply.pngReply
Comment posted by
Daniel Scharrer
Mar 10, 02:00
http://www.nongnu.org/libunwind/docs.html could help move the backtrace generation out of the signal handler
#8
icon_reply.pngReply
Comment posted by
Daniel Scharrer
Mar 13, 16:32
With the crash handler cleanup the crash reporter starts nicely.

When testing there was one time though where the crash reporter was started, but the arx process died before gdb could attach to it. I'll just attribute this to fglrx not liking 32-bit clients on a 64-bit system.

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from New to Fixed.
  • This issue's progression has been updated to 100 percent completed.
  • The resolution has been updated, from Not determined to RESOLVED.