[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #30477] "help" command hangs because SIGCHLD h

From: Alex Lancaster
Subject: [Octave-bug-tracker] [bug #30477] "help" command hangs because SIGCHLD handler is not async-signal-safe
Date: Sun, 18 Jul 2010 19:24:49 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100622 Fedora/3.6.4-1.fc13 Firefox/3.6.4


                 Summary: "help" command hangs because SIGCHLD handler is not
                 Project: GNU Octave
            Submitted by: alexl
            Submitted on: Sun 18 Jul 2010 12:24:48 PM MST
                Category: Interpreter
                Severity: 3 - Normal
              Item Group: Crash
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 3.2.4
        Operating System: GNU/Linux



A downstream user, Matt McCutchen, has submitted the following bug report of
a hang in our Bugzilla instance:


The backtrace is here:


I can't reproduce the problem myself, but here's his description for how to
reproduce it:

"Description of problem:
Octave's SIGCHLD handler calls operator new, which is not async-signal-safe. 
This can cause the "help" command to hang if the SIGCHLD from the info
subprocess arrives while octave was already in a call to operator new.

Version-Release number of selected component (if applicable):

How reproducible:
Rarely and randomly.  I haven't found any tricks to make it happen more

Steps to Reproduce:
1. Start octave.
2. help clear

Actual results:
Octave hangs (see attached backtrace).

Expected results:
The "help" command completes. "


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]