public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/17244] New: trunk/sysdeps/unix/sysv/linux/semctl.c:116: va_args muxup ?
Date: Fri, 08 Aug 2014 08:35:00 -0000	[thread overview]
Message-ID: <bug-17244-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 17244
           Summary: trunk/sysdeps/unix/sysv/linux/semctl.c:116: va_args
                    muxup ?
           Product: glibc
           Version: 2.21
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: dcb314 at hotmail dot com
                CC: drepper.fsp at gmail dot com

[trunk/sysdeps/unix/sysv/linux/semctl.c:116]: (error) va_start() or va_copy()
called subsequently on 'ap' without va_end() inbetween.
[trunk/sysdeps/unix/sysv/linux/semctl.c:122]: (error) va_list 'ap' used before
va_start() was called.

For function __new_semctl, one two many calls to va_start
and va_end.

  va_start (ap, cmd);

  /* Get the argument only if required.  */
  arg.buf = NULL;
  switch (cmd)
    {
    case SETVAL:        /* arg.val */
    case GETALL:        /* arg.array */
    case SETALL:
    case IPC_STAT:      /* arg.buf */
    case IPC_SET:
    case SEM_STAT:
    case IPC_INFO:      /* arg.__buf */
    case SEM_INFO:
      va_start (ap, cmd);
      arg = va_arg (ap, union semun);
      va_end (ap);
      break;
    }

  va_end (ap);

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


             reply	other threads:[~2014-08-08  8:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08  8:35 dcb314 at hotmail dot com [this message]
2015-09-16 12:53 ` [Bug libc/17244] " cvs-commit at gcc dot gnu.org
2015-09-16 13:05 ` schwab@linux-m68k.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-17244-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).