#11994 BLOC 12.1.0: runin-gtk crashes with segmentation fault

Zarro Boogs per Child bugtracker at laptop.org
Fri Jul 6 13:44:49 EDT 2012


#11994: runin-gtk crashes with segmentation fault
---------------------------------------------+------------------------------
           Reporter:  greenfeld              |       Owner:  Quozl                            
               Type:  defect                 |      Status:  new                              
           Priority:  blocker                |   Milestone:  12.1.0                           
          Component:  manufacturing process  |     Version:  Development build as of this date
         Resolution:                         |    Keywords:                                   
        Next_action:  reproduce              |    Verified:  0                                
Deployment_affected:                         |   Blockedby:                                   
           Blocking:                         |  
---------------------------------------------+------------------------------

Comment(by dsd):

 The core file doesn't seem that useful unfortunately. Here are some other
 ideas:

 I suspect the segfault may happen soon after system resume (so far running
 aggressive suspend seems to be the best way to reproduce this). This can
 be confirmed with the following change in runin-main:

 {{{
 -/usr/bin/xinit $RUNIN_PATH/runin-tests $* -- &> $LOG_PATH/run.log
 +/usr/bin/xinit $RUNIN_PATH/runin-tests $* -- &> /dev/kmsg
 }}}

 The segfault will now be logged to the kernel logs, which also show us
 when suspend/resume is happening.

 Another suspicion, it could be linked to signal handling. So in addition
 to the above, lets modify runin-tests to log when it is sending signals.
 Inside the "while true" loop:
 {{{

         echo "Suspend cycles : @${SUSCNT}"
         echo "@@ $ELAPSED_TIME $RUNIN_TIME"
      ) > $RUNIN_STATUS
 +       echo "Send signal for GUI update"
      kill -USR1 $GTK_PID
 }}}

 It would also be worth capturing the crash live in gdb, rather than using
 core files. Sometimes this works better. gdb could be attached to the
 runin-gtk process over serial or in the ENABLE_DEBUG debug console.

-- 
Ticket URL: <http://dev.laptop.org/ticket/11994#comment:12>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system


More information about the Bugs mailing list