Bug 695674 - warning: dereferencing type-punned pointer will break strict-aliasing rules
Summary: warning: dereferencing type-punned pointer will break strict-aliasing rules
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xinetd
Version: 5.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Vojtech Vitek
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 697783
TreeView+ depends on / blocked
 
Reported: 2011-04-12 11:46 UTC by Vojtech Vitek
Modified: 2015-03-04 23:57 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 697783 (view as bug list)
Environment:
Last Closed: 2011-05-25 08:38:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Patch to fix the warning and possible corruption of the time_t variable (870 bytes, patch)
2011-04-12 11:49 UTC, Vojtech Vitek
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0827 0 normal SHIPPED_LIVE xinetd bug fix update 2011-05-25 08:38:48 UTC

Description Vojtech Vitek 2011-04-12 11:46:39 UTC
There is *Testsuite regressions* detected in the xinetd package:

352  sensor.c: In function 'process_sensor':
353  sensor.c:110: warning: dereferencing type-punned pointer will break strict-aliasing rules

I will provide a patch in next comment.

Comment 1 Vojtech Vitek 2011-04-12 11:49:33 UTC
Created attachment 491463 [details]
Patch to fix the warning and possible corruption of the time_t variable

Comment 6 errata-xmlrpc 2011-05-25 08:38:54 UTC
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 therefore 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.

http://rhn.redhat.com/errata/RHBA-2011-0827.html


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