Bug 128091 - sigishandled() misbehaviour due to bug in parse_sigset_t()
sigishandled() misbehaviour due to bug in parse_sigset_t()
Product: Fedora
Classification: Fedora
Component: strace (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Roland McGrath
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2004-07-17 11:44 EDT by Dmitry V. Levin
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-31 22:02:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
strace-4.5.5-alt-parse_sigset.patch (560 bytes, patch)
2004-07-17 11:45 EDT, Dmitry V. Levin
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2005:131 normal SHIPPED_LIVE strace bug fix update 2005-05-19 00:00:00 EDT

  None (edit)
Description Dmitry V. Levin 2004-07-17 11:44:26 EDT
When traced process receives signal which will be handled, strace may
decide that process is going to die and will detach from this process.

It happens because sigishandled() sometimes incorrectly returns 0 due
to hex string parser bug in parse_sigset_t().
Comment 1 Dmitry V. Levin 2004-07-17 11:45:49 EDT
Created attachment 102000 [details]

Proposed patch.
Comment 2 Roland McGrath 2004-08-31 03:01:03 EDT
Fix in upstream.
Comment 3 Roland McGrath 2004-08-31 22:02:06 EDT
4.5.7-2 is in rawhide.  I'll make an FC2 update release in a few days.
Comment 4 Tim Powers 2005-05-19 17:09:55 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.