[Bug 1154] New: gsmd at 100% CPU (sigsegv-handling problem)

[bugzilla-daemon at bugzilla.openmoko.org]

http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1154

           Summary: gsmd at 100% CPU (sigsegv-handling problem)
           Product: OpenMoko
           Version: current svn head
          Platform: Neo1973
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gsmd
        AssignedTo: tick at openmoko.com
        ReportedBy: mail at mmontour.net
                CC: buglog at lists.openmoko.org


A few times now I have seen my recent MokoMakefile-built gsmd (package version
0.1+svnr3759-r40) get stuck at 100% CPU. I ran 'strace -p' on its PID and saw
lots of the following:

Process 2353 attached - interrupt to quit
--- SIGSTOP (Stopped (signal)) @ 0 (0) ---
--- SIGSTOP (Stopped (signal)) @ 0 (0) ---
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
sigreturn()                             = ? (mask now [])

The gsmd.c code calls "signal(SIGSEGV, sig_handler);" (along with 4 other
signals), but the switch statement in the sig_handler() function does not have a
case for SIGSEGV. I do not know what initially triggered the problem, but it
looks like an un-handled segfault is causing the 100%-CPU looping.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.