public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mliska at suse dot cz" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29279] New: undefined reference to `mbstowcs_chk' after 464d189b9622932a75302290625de84931656ec0
Date: Thu, 23 Jun 2022 13:44:12 +0000	[thread overview]
Message-ID: <bug-29279-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 29279
           Summary: undefined reference to `mbstowcs_chk' after
                    464d189b9622932a75302290625de84931656ec0
           Product: glibc
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: mliska at suse dot cz
                CC: drepper.fsp at gmail dot com, goldstein.w.n at gmail dot com
  Target Milestone: ---

After the revision, the following fails:

$ cat /tmp/x.c
#include <stdlib.h>

const char *name;
int len;

int main()
{
        if (mbstowcs (NULL, name, len) ==  -1)
              return 0;
}

$ gcc /tmp/x.c -D_FORTIFY_SOURCE=2 -O2
/usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld:
/tmp/ccWxqRJf.o: in function `main':
x.c:(.text.startup+0x15): undefined reference to `mbstowcs_chk'
collect2: error: ld returned 1 exit status

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

             reply	other threads:[~2022-06-23 13:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23 13:44 mliska at suse dot cz [this message]
2022-06-23 13:44 ` [Bug libc/29279] " mliska at suse dot cz
2022-06-23 13:49 ` siddhesh at sourceware dot org
2022-06-23 15:28 ` goldstein.w.n at gmail dot com
2022-06-27  1:48 ` siddhesh at sourceware dot 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-29279-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).