[Bug libc/11522] Uninitialised Variable in qsort_r

[Bug libc/11522] Uninitialised Variable in qsort_r

[fweimer at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=11522

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |security-

--- Comment #2 from Luís Fernando Schultz Xavier da Silveira <lfsxs0 at gmail dot com> ---
Subject: Re:  New: Uninitialised Variable in qsort_r

Sorry for this and thank you for your attention.

On Tue, Apr 20, 2010 at 03:33:23AM -0000, lfsxs0 at gmail dot com wrote:
> In short, the following extract from stdlib/msort.c, lines 182-185, shows the
> variable phys_pages is used before initialization in a zero comparison. Is this
> legal?
> 
> static long int phys_pages;
> static int pagesize;
> 
> if (phys_pages == 0)
> 
> Furthermore, I have a question about qsort opening the /proc/meminfo file to get
> the total available memory: I run ACM-ICPC-like contests and use a ptrace-based
> sandbox software I wrote exactly for this. It keeps reporting a contestant is
> opening a file when he/she is actually just qsort'ing some array. Is there a way
> to prevent this behaviour?
> 
> Thank you.
> 
> -- 
>            Summary: Uninitialised Variable in qsort_r
>            Product: glibc
>            Version: 2.10
>             Status: NEW
>           Severity: normal
>           Priority: P2
>          Component: libc
>         AssignedTo: drepper at redhat dot com
>         ReportedBy: lfsxs0 at gmail dot com
>                 CC: glibc-bugs at sources dot redhat dot com
>  GCC build triplet: x86_64-pc-linux-gnu
>   GCC host triplet: x86_64-pc-linux-gnu
> GCC target triplet: x86_64-pc-linux-gnu
> 
> 
> http://sourceware.org/bugzilla/show_bug.cgi?id=11522
> 
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-24817-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon Jun 30 15:06:44 2014
Return-Path: <glibc-bugs-return-24817-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 18319 invoked by alias); 30 Jun 2014 15:06:43 -0000
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
Delivered-To: mailing list glibc-bugs@sourceware.org
Received: (qmail 18123 invoked by uid 48); 30 Jun 2014 15:06:34 -0000
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/12153] use of keywords in macro definitions can make compilation fail
Date: Mon, 30 Jun 2014 15:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: libc
X-Bugzilla-Version: 2.11
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: drepper.fsp at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: security-
X-Bugzilla-Changed-Fields: resolution
Message-ID: <bug-12153-131-rMhUZgQJ17@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-12153-131@http.sourceware.org/bugzilla/>
References: <bug-12153-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-06/txt/msg02193.txt.bz2
Content-length: 694

https://sourceware.org/bugzilla/show_bug.cgi?id\x12153

Joseph Myers <jsm28 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|WONTFIX                     |INVALID

--- Comment #9 from Joseph Myers <jsm28 at gcc dot gnu.org> ---
It was agreed by WG14 that such definitions of keywords as macros were never
intended to work when macros defined in system headers are expanded, and the
standard wording was fixed in C11; it now says "or when any macro defined in
the header is expanded".

--
You are receiving this mail because:
You are on the CC list for the bug.

[Bug libc/11522] Uninitialised Variable in qsort_r

[aj at suse dot de]

------- Additional Comments From aj at suse dot de  2010-04-20 07:22 -------
A static variable is initialised as zero according to the C standard.  So,
there's no bug here.

I cannot help you with your other problem.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID


http://sourceware.org/bugzilla/show_bug.cgi?id=11522

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